|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Pure Access API v2 (ranked 3653 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/3fo8iziHfvZ8zkKgQzEpN_pure_access_api_v2_json.jsonGENERAL INFORMATION
All times are UTC. Rate limiting can vary by endpoint.
Changelog 1.0.5
- Updated with changes for the Pure Access 4.0.0 release
- POST, PUT, PATCH /users - areaId on the user object is no longer read only, if this property is omitted the tenant default will be selected for the user as it was previously.
- POST, PUT, PATCH /credentials - you will need to send credential information differently if the tenant is integrated with ENGAGE. Credentials added before a tenant is linked to ENGAGE must go through a migration process in order to be properly sent to and read by Schlage devices.
- Added support for Schage Mobile Access Bluetooth credentials. ISONAS Bluetooth credentials are not supported on Schalge devices and the Schlage Mobile Access credential is not supported on ISONAS devices. Only the Schage Mobile Access credentials can be enrolled by sending a text message to the desired recipient using the "mobileNumber" field.
- /commands new command for Schlage devices
- /users now i
...
Contact
- Name: product@isonas.com
SECURITY 3/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API5:2023, API7:2023
PERFORMANCE 2/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 671 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 3/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 3.0.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!