|API RANK| by Escape.tech

Benchmark and ranking of 5138+ public APIs by Escape.tech

Back to the list Request ranking update

GENERAL INFORMATION

<h2>Instructions</h2>To use the REST API. Use the following POST command. Add the variables in the URL.
Remember to keep your API keys private, do not call from client side javascript on a website. Make
sure to add your secret key to the header of the API, key=x-api-key value= your secret.

We have test APIs which give a sample response back and production APIs that remove credits.
If the API key is not correct or missing, you will get a 401 Unauthorized error response.

Note, APIs with signature and Photo may cost more credits. Use the basic API, /nid-person if you don't need a photo.

Note check-person and check-nid are the same except that in check-nid you pass the data object in the body vs using
url parameters. Photo response is base64 image as a string.

<h2>Optional Tracking</h2>
To all the request objects, a string variable team_tx_id may be added to track the transaction. This is a value or ID from your system you can use to help compare repo

...

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 2/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 743 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.1 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!

Last scanned: 5/4/2023