|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
TMQuotes API Platform (ranked 3997 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/5i_PgyHuzzDrb1j6Qj3fv_tmquotes_api_platform_json.jsonGENERAL INFORMATION
TMQuotes REST API Platform lets agents integrate with TMQuotes to get valid lists of plans and quotes to support various customer journeys. This could be anything from a chatbot flow to custom forms.
Understanding the APIs at a Glance
The 3 main categories of the platform: 1) Plans, 2) Quotes, and 3) Purchase (Future Release).
Browse Plans
Build inventory of available plans with /plans
. All plans are associated with a Plan Category. Within the Plan Category you'll find plans and plan details. The plan schema is the same for all categories.
Quotes
With trip details passed in the request, you can get a quote within a plan category with /quote/{Plan_Category}/
. Difference plan categories have different request body parameters.
Purchase
Today, with v1
, a plan has a purchase_form_link
attribute, which will take the user through the existing UI for your subdomain when they follow the link. The form UI is already de
...
Contact
- Name: API Support
- Name: apiinfo@tmquotes.com
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: A05:2021
PERFORMANCE 1/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 870 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!