|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Agreement Integration (ranked 4023 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/eLvW0I4XweT87v3sc333Z_agreement_integration_json.jsonGENERAL INFORMATION
The 'Agreement' integration focuses on allowing 3rd party systems to sync contacts / properties from Palace and create new 'Owners', 'Properties', 'Tenancies' and 'Sub-Tenants'. It also allows for sending official 'Agreements' back to Palace as a file document (PDF Recommended).<BR><BR>The 'Agreement Integration' area does NOT require an upgrade from a 'Standard' API account to a 'Premium' API Account. There is a NO cost involved in using these contracts unless you are a 3rd Party solution provider wanting to integrate at a partner level.<BR><BR> Along with the CRM contracts, the system also includes an 'Available Property' contracts for those specifically wanting to display properties that available to tenanted only.<BR><BR>NOTE: For supporting contracts to obtain further codes for the CRM insert functionality please review the CRM Contracts available at https://app.swaggerhub.com/apis-docs/Palace/CRM_Integration/2.0.0
Contact
- Name: development@getpalace.com
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API7:2023
PERFORMANCE 1/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 965 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 2/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 2.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 0/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!