ezDispatch (ranked 65 of 5138)https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/RTEaGsPme434aOinu5Uek_ezdispatch_json.json
Reference documentation for ezDispatch API v1 which is currently being built to match these specfications.
This API will use Basic Auth and username and password will be generated for access. To use the Swagger mock server you can omit the authorization header.
To test endpoint, click through the documentation below. By clicking on the "Try it out" and then "Execute" button you'll see a sample output. You'll also get a curl reference and a "Request URL" you can use in your application. While using the mock server be sure to include the proper accept header as well.
- Name: firstname.lastname@example.org
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: A05:2021
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 44.7 ms .
Get p50 under 220 ms to get a 4/5 score.
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.
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.
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!