|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Catalogue API Specification (ranked 1112 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/qXHjNVUx70LQQGsqapTDL_catalogue_api_specification_json.jsonGENERAL INFORMATION
API specification for catalogue information. Uplifted version 2.1 contains the uplifted product object model used for put operation in /products and /products/<guid>.Also put operation introduced for other catalogue item resources. Ver 2.2 uplifted to remove editorial version from product data model and instead add contentprovider Id. ver 2.3 uplifted to include transactionId as a transient field. version 2.4 added the post operations for /programs and /programs/<guid> and pricing roll up changes related 2.6 version is created after adding pricingStartDate,pricingEndDate fields to brand collection and season data model. version '2.7' to uplift the collection operations and data model for product. Version '2.8' to uplift the Program resource data model to include the context aware offer and other dates using productAssociationDetails. Version'2.9' is uplifted to include the parentEditorialVersion in parentInfo data model referenced in product data model and removed dates from anchor dat
...
Contact
- Name: xyz
- Name: xyz@bt.com
SECURITY 5/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP: We didn't find any OWASP vulnerability.
PERFORMANCE 1/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 799 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 2.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 2/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!