|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Pin Hype Api (ranked 3826 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/h_e8oBUjklywuw2aDrgc4_pin_hype_api_json.jsonGENERAL INFORMATION
Introduction
This is an API that aims to integrate partners who want to offer our product catalog quickly and practically.
What is Pin Hype?
Pin Hype is a credit or game key redemption platform development by Level Up! Interactive, the leading game publisher in Latin America since 2004.
Player page to redeem a Pin Hype
https://redeem.hype.games
How to Authenticate?
The authentication data (identifier
and secret
) is shared at the beginning of the developed by email, request the authentication data by email partner.hype@levelup.com.br
For token authentication we use JSON (JSON Web Tokens) https://jwt.io/introduction/
What is JSON Web Token?
JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be sig
...
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 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 788 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!