|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Antikvariaatti.net API (ranked 2669 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/9Ji9mghh0QilAVDKYWW_f_antikvariaatti_net_api_json.jsonGENERAL INFORMATION
Antikvariaatti.net product and order APIs.
All queries need to be authenticated by adding the issued
API key to request header 'apikey'.
Antikvariaatti.net APIs implement a rate limit with a leaky bucket
algorithm for rate limiting. The common quota is 60 requests per
minute (subject to change). Current state of bucket is returned
in a (successful) request's response header 'x-bucket-state',
formatted as items / bucketsize. If the bucket overflows, a
429 response is returned.
Please see the notes on using curl with POST
/product/:productId/images; this API does NOT support HTTP 100
expect-continue flow.
Note that some endpoints may be flagged as beta, and they are
available for beta testing customers only; merchants are
welcome to participate!
Version history:
- 0.1.0: Initial version
- 0.1.1: First public release
- Added a category hierarchy (path) to GET /categories for context
- Added a new endpoint /product/:id/images/import for importing
products f
...
Contact
- Name: tuki@antikvariaatti.net
License
- Name: All rights reserved - contact for licensing options
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 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 351 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!