|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
nova ava - REST API (ranked 1890 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/JgrT7qNo6FqZc68Vllu6__nova_ava___rest_api_json.jsonGENERAL INFORMATION
Authentication
You can choose between two available methods: Basic Auth
or Bearer Token
.
In each HTTP request, one of the following HTTP headers is required:
Basic Auth - Authorization: Basic base64_encode('email:API_KEY')
Bearer Token - Authorization: Bearer API_KEY
<br>
Connect via base URL https://api.avanova.de/v1
If you are using the base URL to connect to the API, you need to sent the HTTP header TENANT
with your account permalink. The permalink is the subdomain part of your account URL [TENANT].avanova.de
.
<br>
Connect via account URL https://[TENANT].avanova.de/api/v1
Alternatively you can connect directly to your account without the need of sending the TENANT
header.
<br>
Limitations
Requests are limited to 60 per minute.
If the limit is exceeded, you will receive the HTTP error: 429 Too many requests
All result lists are limited to 100 by default. This limit can be increased by the query parameter limit
to a maximum of 1000.
...
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: A05:2021
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 107 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 2.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!