|API RANK| by Escape.tech

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

Back to the list Request ranking update

GENERAL INFORMATION

Purpose of this document

This document describes the RESTful APIs available on the Game System Authentication Server (Auth Server).

RESTful approach

Conventions

This server exposes its capabilities via a set of RESTful web services. The types of clients we would expect to connect to this API would include web based systems (either javascript clients or server side code) and mobile applications for Android or iOS devices.
API calls being are made over HTTPS and using the HTTP methods POST, PUT, GET and DELETE as verbs.

  • GET is used to query or return one or more resources.
  • POST is used to create new resources either individually or in a batch. This is used where the server creates ids for the resources to be managed. The POST returns the IDs of the created resources.
  • PUT is used where an existing resource is to be modified.
  • DELETE will delete a resource.

Beyond the use of HTTP verbs the following are important:

  • GET Retrieves data only. It is safe in that it does no

...

SECURITY 3/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, API5:2023

PERFORMANCE 0/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 1,640 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!

Last scanned: 5/4/2023