EnglishGetting started
Errors
Handle errors by HTTP status and never retry every failed request blindly. Always send Accept: application/json.
StatusWhat to do
400Invalid parameter or page-size limit. Correct the request; do not retry unchanged.
401 / 403Missing, invalid, expired or inactive key, or source access denied. Check the response and subscription; do not retry unchanged.
404Vehicle or lot not found. Show an empty result; do not invent a price.
429Request limit reached. Honor Retry-After when provided; use bounded backoff and account for your plan budget.
5xx / timeoutRetry safe reads only, with a bounded retry budget. Keep the last successful checkpoint and avoid logging keys or full responses.
Authentication errors
- 403
{ "error": "please add auth key in x-api-key header" } - 403
{ "error": "wrong api key" } - 403
{ "error": "your api subscription has expired" } - 403
{ "error": "your api subscription is not active" }
Read the response safely
- Application checks normally return an object with error; framework and gateway failures use message.
- A gateway, proxy or web server can return HTML, plain text or an empty body even when JSON was requested.
- Retry only safe GET requests, with a bounded budget and increasing delays. Keep your last successful checkpoint.