|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Emerge Public API (ranked 3208 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Cw4pnZb1eYbRKHq3U7irS_emerge_public_api_json.jsonGENERAL INFORMATION
The Emerge public API provides partner developers with access to core capabilities of the Emerge platform.
The current version of the API is v1.1.4. This API will evolve as the features in Emerge's product evolve.
Get Started
The Emerge API is a 'restish' API and is designed to allow you to work with objects using familiar HTTP verbs like
- POST
- PUT
- DELETE
- GET
All production level API requests are made to:
<br />https://api.emergemarket.io
The testing sandbox is available during development and for testing:
<br />https://demo-api.emergemarket.dev/
Workflow
The Emerge API is designed to support two primary workflows: An opportunity-to-tender workflow and an opportunity-to-award workflow.
Opportunity-to-tender
The opportunity-to-tender is the most common workflow of an integrating system. In this workflow, the Emerge system is used to source the live capacity as well as to tender through Emerge to that live capacity. The benefit of this workflow is that all info
...
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 2/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 650 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 3/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!