|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Renewables API (ranked 1081 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/XAnYe6hhyavYWXWFrwRJy_renewables_api_json.jsonGENERAL INFORMATION
Last Updated: Januray 9th, 2019
General Information
This document contains information for developers, on how to use the enmacc Renewables API. Use this API to send, retrieve and delete orders for renewable products on the enmacc platform. This functionality is seamlessly integrated into enmacc CONNECT and uses the same authentication workflow and usage plans. See the enmacc connect documentation for more information: enmacc CONNECT documentation
Prices always have to consist of a value and a currency. For GoOs only EUR is allowed. Orders can be marked as partially executable, meaning not their entire available quantity has to be traded at once. However, once all of the available quantity of an order has been traded it will become unavailable. Every order has to specify an expiration date-time down to a minute precision. Seconds and milliseconds should always be zero. As long as the order has not expired and stil has some availabl
...
Contact
- Name: Enmacc GmbH
- Name: info@enmacc.de
- 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 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 64.8 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!