|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
DNSFilter API (ranked 4294 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/_yH2PyLHYSNQRnogBE0im_dnsfilter_api_json.jsonGENERAL INFORMATION
DNSFilter API Documentation for Developers.
NOTE: Our API is fairly stable, but we are continuing to make fixes before we finalize our version 1 API. We will do our best to communicate any breaking changes to the API before they happen.
The API was designed using json:api specification when possible, please visit the page to read about it and get familiar with the requests/responses structures.
Errors
The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format:
{
"error": "Not Authorized"
}
Authentication
Authentication is required for almost all API endpoints. The client has to send authentication details in the request header Authorization with a valid Auth0 token, Authorization value looks like token <JWTTOKEN>.
Obtaining a Token
Authentication tokens can be obtained from our Auth0 API instance using the [Authenticate API `/oauth/to
...
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: A05:2021, A07:2021
PERFORMANCE 1/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 890 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 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!