|API RANK| by Escape.tech

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

Back to the list Request ranking update

GENERAL INFORMATION

Authentication for the API requires performing a login on the site, either in a browser or through a mobile web view. This is required as the authentication is performed via Microsoft Azure B2C.

To initiate the login, perform the following steps:

  1. Ask the user for their employer key.

  2. Request https://devlogin.mybenefits.life/api/v1/site with the user's employer key. If the response returns enableAnonymousViewing=true, prompt the user to either login/register or continue without logging in/registering (flow A). If it returns enableAnonymousViewing=false, immediately continue to the login/register flow below (flow B).

Flow A: If the user chooses to login/register:

  1. Load https://devlogin.mybenefits.life/login?returnUrl=/complete

  2. The browser will be redirected to a Microsoft B2C login page where the user will enter their credentials or register.

  3. The user will be redirected to https://devlogin.mybenefits.life/complete.

  4. If the user has not completed the re

...

SECURITY 2/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, API3:2023

PERFORMANCE 3/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 429 ms .

Get p50 under 220 ms to get a 4/5 score.

RELIABILITY 0/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 returned 5xx errors.

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!

Last scanned: 5/22/2023