The state of public APIs| Submit an API

|API RANK| by Escape.tech

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

Back to the list Request ranking update

OpenRouteService API (ranked 647 of 5138)

https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/OpmV6lqUK5vnTfGuBbh_O_openrouteservice_api_json.json

GENERAL INFORMATION

This is the documentation for the OpenRouteService API.
For an API-Key please register at our developers portal.
Afterwards the Key can be requested in the API catalogue.

Instructions:
To send actual requests authorization is needed:

  • on swaggerhub: Click the green Authorize button and enter your API-Key
  • in the API Catalogue: Insert your API-Key in the API Key field at the top of the page. (In case of an 'Authorization Error' please reload the website and insert your Key again.)

To fire a request:

  • on swaggerhub: click on the Try it out button, specify parameters and click the execute Button at the bottom of the corresponding parameter section.
  • in the API Catalogue: specify the parameters first and then press the Try it out! Button below the Response Messages Section.

Swaggerhub additionally generates a curl c

...

Contact

  • Name: openrouteservice@geog.uni-heidelberg.de

License

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 98.4 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 2.0 schema specification.
  • Contains comments and summaries.
  • Contains examples.
  • Does not contain duplicated objects.

Popularity 1/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