|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Third Party API Integration (ranked 4090 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Z0cVD05q571vDgLfRe3g7_third_party_api_integration_json.jsonGENERAL INFORMATION
The services given in this document for creating booking on third party systems. The bookings once created will be received on the sun telematics platform.
Explanation of the Booking Api keys is mentioned below.
"key": {This will be a secured key shared by Sun Telematics to BTR. This key will be passed as the Authorization header while calling this api},
"vendor_id": {This is a partner code, mutually decided between BTR and SunTelematics, Will be same for all the Bookings}
"partner_name": { Will always be BTR , it will use by the sun telematics to identify that the booking is from the BTR }
"order_reference_number": {This will be the Booking reference id Of partner, always unique for each Booking"}
"passenger_name": {Name of the passenger travelling}
"passenger_email": {Email id of the passenger}
"passenger_phone_number": {Phone
...
Contact
- Name: Abhishek Jha
- Name: abhishek@suntelematics.com
SECURITY 5/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP: We didn't find any OWASP vulnerability.
PERFORMANCE 0/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 5,000 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!