|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Megabuyte External API (ranked 1455 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/TN3azBhDTyTMcvKrZfRJC_megabuyte_external_api_json.jsonGENERAL INFORMATION
All data retrieval operations require authentication.
- Authentication is token based.
In order to authenticate and start using the API:
- Contact Megabuyte to obtain your user credentials
- Use login endpoint to retrieve authentication token. Token is valid for 24 hours
- Each data request should have the token included as the
Authorisationheader - If token expires, http error code
401will be sent back as a result of the API call
Making API calls using this page
In order to try the API using this page:
- Contact Megabuyte to obtain your user credentials
- Call Login method with credentials to get an authentication token. Copy the token
- Press Authorise button and paste the token
- Now you can make Data retrieval calls by using appropriate query options, as documented
Data objects identifiers
- Property
mbIdrefers to the internal Megabuyte id of the entity - Property
companiesHouseIdsrefers to the Companies House ids of
...
Contact
- Name: admin@megabuyte.com
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 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 130 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!