Documentation

To ensure efficient use and fair distribution of resources, our platform implements API rate limiting. Rate limits are in place to maintain platform stability and to ensure fair access for all users.

Rate Limit Overview

Strict Limits

Certain APIs are strictly limited to one request per second. This restriction is in place to prevent excessive use of resources and to maintain optimal performance for all users. The restricted APIs subject to this one request per second limit include:

1. Auction
2. Europe VIN Decode
3. Europe VIN Decoder
4. License Plate OCR
5. Title Check
6. US Plate Decode
7. US Truck Plate Decode
8. VIN OCR
9. VIN Suggestion
10. Vehicle History
11. US Plate Decoder

Package-specific Limits

The rate limit may vary from package to package. It is essential to review the documentation for each package to understand the specific rate limits imposed. Apart from above mentioned APIs in "Strict Limits" section all other APIs will follow rate limiting based on the package users will subscribe to. Please find the rate limits based on packages on www.vehicledatabases.com/portal/package

Rate Limit Exceeded

If the quota is exceeded, the API will respond with an HTTP status code 429, indicating that the rate limit has been exceeded. Along with the error code, the API will return an error message stating, Rate limit is exceeded. Try again later. This message serves as a notification to the user that they have reached the rate limit and should adjust their request frequency accordingly.

Ensuring Compliance

Developers utilizing our APIs should implement logic within their applications to handle rate limit responses gracefully. This includes implementing appropriate retry mechanisms to prevent overwhelming the API with repeated requests.