|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Autostore Public API (ranked 2004 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/CZhTL0xdH0uoLFT5mikvK_autostore_public_api_json.jsonGENERAL INFORMATION
The AutoStore Warehouse Management Service provides a Turnkey Solution for managing a wide variety of warehouse fulfillment scenarios.
In order to simplify integrations, we have developed a flexible Partner API that allows a robust and resilient integration using a powerful REST API, and asynchronous event feed. The API is based on standard HTTP verbs and accepts and returns JSON encoded documents
The below-documented API calls provide a base set of functionality that allows several integrations with the AutoStore Fulfillment Platform. The document does not stand by itself but is a companion during any integration project. The usage may be specific to the operational flows chosen for the project.
The core integration feature set allows:
- Catalog Synchronization
- Order Synchronization
- Pick Synchronization
- Put-Away/Induction management
- Inventory Quality Control Management: holds, cycle counts, ...
- Event notification or subscription
- ...
This list of Integration endpoint
...
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: A05:2021
PERFORMANCE 3/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 394 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!