|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Cloudonix API.Core - Domain Level Privileges (ranked 3209 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/KsXHbrt0Gn_uqqkK59Hbj_cloudonix_api_core___domain_level_privileges_json.jsonGENERAL INFORMATION
Cloudonix API.Core services are the backbone of all data management
and access to the Cloudonix SaaS platform. It maintains all data
models and offers authenticated APIs to perform business operations on
the them.
Remote Application Access
Cloudonix API calls must each be authorized using an Authorization
header containing an API key “key id” as a bearer token
. When handling
any and all such calls, the caller must make sure to send an Authorization
header in the HTTP request, whose content is the keyword Bearer followed
by a space and the caller’s API key’s “key id” field. The server will
reject any insufficiently authorized calls with a 401 Unauthorized
HTTP error response - in the following cases:
- The Authorization header is not set or not correctly formatted.
- The provided key does not match a known and active API key
- The API key is not authorized for the call that is being performed.
API Privileges
While all API.Core API calls require authorization
...
Contact
- Name: ops@cloudonix.io
- Contact API maintainers
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 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 399 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!