|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Digital agendas interconnexion (ranked 934 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/AqzEHYjl7L73KfJvVBRVh_digital_agendas_interconnexion_json.jsonGENERAL INFORMATION
Hi there! Welcome to this documentation.
From fragmentation to interconnection
You are here because data silos, between platforms hosting digital agendas used in BtoB transport and logistics, are detrimental to business optimization.
You want to allow your platform users to get access to agendas hosted by others platforms?
Use this API! It allows a standardised interconnection between platforms hosting digital agendas used in BtoB transport and logistics.
A sandbox at your disposal
To facilitate this interconnection, we provide a sandbox that allows you to test, without any real-world impact, the ability of your platform to :
- Consult agendas hosted by other platforms.
- Make appointments in this inter-platform context.
- Delete appointments in this inter-platform context.
- Update data associated with appointments in this inter-platform context.
Contact GS1 France to get access to this sandbox.
[***When Logist
...
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 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 10.9 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!