|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Greenbox API (ranked 2036 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/OsT0gAQWUrKw7Mu8ygxPQ_greenbox_api_json.jsonGENERAL INFORMATION
API for communication with devices and device data operations.
Identifiers
Application ID
Greenbox data model is designed to work with multiple applications simultaneously.
In order to distinguish between the applications a unique application integer ID has to be used.
It is a caller responsibilty to select proper application ID.
Device ID
Since connector can implement custom binary network protocol,
it is most likely it will use some binary representation of device identifier (4-byte integer for example).
On the other side there might be a different requirement on how to identify device from the application point of view.
Therefore we distinguish between two types of device identifiers - a physical device ID and a virtual device ID.
Variable ID
Same as for device ID, variable IDs can have different representations based on where they are needed.
For example, 2-byte identifier for the device internal processing and network transfers
vs.
...
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: API7:2023, API5:2023
PERFORMANCE 5/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 26.5 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!