|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Mobile Locker - Zetes api (ranked 1071 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/ldxliyYY4hVdVyQAVe4Wq_mobile_locker___zetes_api_json.jsonGENERAL INFORMATION
Mobile Locker zetes API
Authentication
Our application uses oauth authentication. You will receive a client id and a client secret that you will need to fetch the access token. You can find more about this on https://doc.oroinc.com/api/authentication/oauth-client-credentials/
Terminology
unit = container containing the computer + screen + bar code scanner + …
Locker-unit = Container containing the lockers
A unit can be placed inside a locker-unit or can be stand-alone. That is why we split up unit and locker-unit. Later on, if we need more capacity on a location, a new locker-unit can be placed and be hooked up to the existing unit on that location.
Callbacks/Web hooks
The application sends a web hook when certain events occur. (Locker opened, Locker closed, ...) with a POST request containing all the relevant data.
The URL is configurable in the system per unit, but it's likely that only one is used over the entire system.
The system will retry the request every 5 minutes
...
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 4/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 77.9 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 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!