|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Synccentric module for Chaim (ranked 2288 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/stpEjVQfnatH_XIGiZJ9R_synccentric_module_for_chaim_json.jsonGENERAL INFORMATION
Integration requires sending identifiers via API to data storage or by dropping a file to an ftp directory, lowest offers are retrieved by rate limit (1,000,000 per day), export files are generated and stored on server for Chaim to collect via FTP or via API endpoint
API endpoints will cater to the following actions each are separated by Lowest offer module and Seller account integration module
<br> <br>
lowest offer module endpoints:
- Import ASIN(s) to data Module storage
- Delete ASIN(s) from data Module storage
- Export lowest offer data
Seller account integration:
- initiate import
- View Data in Module storage
- Import ASIN(s) to data Module storage
- Delete ASIN(s) from data Module storage
- Update data in Module storage
- Update multiple data in Module storage
- Push(feed) changes to Seller account
- Pull Feed Submission Report
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 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 98.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!