|API RANK| by Escape.tech

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

Back to the list Request ranking update

GENERAL INFORMATION

API Usage from a mobile client

The typical use case for a mobile client of this API is as follows:

  1. Call the Request detailed records for all sites (GET /sites) endpoint for the users' language of choice to completely populate the list of sites. Store the sites_sha1 value from that payload.
  2. On a regular schedule, call the Request a summary of all sites (GET /sites-summary) endpoint to check for changes in the site data. If the summary has the same sites_sha1 that was stored previously, there were no changes. Otherwise, store the new sites_sha1 value and iterate through the client's database of sites:
    1. If the client site_id does not appear in the summary, delete that site from the client database.
    2. If the client changed_ts value is earlier (lower) than that in the summary, temporarily save the corresponding site_id value(s).
  3. If there are saved site_id value(s) from step 2.2, call the Request detailed record(s) for one or some sites (`GET

...

Contact

  • Name: eservices@gov.yk.ca

SECURITY 5/5

The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.

  • OWASP: We didn't find any OWASP vulnerability.

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 203 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 2/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/16/2023