|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Pay Hype API (ranked 3568 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/C6A85ccwwxEoP9PqTdZrg_pay_hype_api_json.jsonGENERAL INFORMATION
Introduction
HYPE is the e-commerce platform developed by Level Up! Interactive, the leading game publisher in Latin America since 2004. Debuted in November 16th of 2016 in Brazil, through HYPE millions of players are able to purchase Steam Keys for different games as well as purchase credits for their favorite online titles.
The objective of this document is to introduce the Hype Payment Service that allow users a fast and practical way to purchase your game credits on a friendly and safe environment, direct through the official game website.
How to Authenticate?
The authentication data (x-payhype-token
and hypeProductId
) is shared at the beginning of the developed by email, request the authentication data by email partner.hype@levelup.com.br
How to Test?
Buyer Details:
Nome: Fernando Pessoa
CPF: Fill as per table above in "Document" column
Data de Nascimento: 13/06/1988
Email: fernando.pessoa@levelup.com.br
Telefone: (11) 95105-582
...
Contact
- Name: partner.hype@levelup.com.br
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 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 805 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!