Error codes
Error response structure
Errors will be returned in either JSON or XML according to the response output format specified in the relevant API call. The error responses all follow the same structure with the error code changing depending on the nature of the error experienced.
Example JSON response
{ "status": 403, "message": "Forbidden", "code": "M03140300", "info": ["Not Authorized"], "more_info": "https://developer.autodata-group.com/docs/read/additional_information/Error_codes", "metadata": { } }
Example XML response
<!--?xml version="1.0"?--> <response> <status>403</status> <message>Forbidden</message> <code>M03140300</code> <info> <item>Not Authorized</item> </info> <more_info>https://developer.autodata-group.com/docs/read/additional_information/Error_codes</more_info> <metadata> </metadata> </response>
Description of error codes
Code | Status | Message | Description |
M03140300 | 403 | Not Authorized |
The API key associated with your request was not recognized or the signature was incorrect. |
M03140301 | 403 | Account Inactive | The API key you are using to access the Mashery API has not been approved or has been disabled. |
M03140302 | 403 | Account Over Queries Per Second Limit | The API key you are using has attempted to access the api too many times in one second. |
M03140303 | 403 | Account Over Rate Limit | The API key you are using has attempted to access the api too many times in the rate limiting period. |
M03140306 | 403 | Service Requires SSL | You need to query the service through SSL protocol. |
M03141400 | 414 | Request-URI Too Long | The requesting URL is too long |
M03150200 | 502 | Bad Gateway | This server received an invalid response from an upstream server it accessed to fulfill the request. If this persists, check our API Status It might be an issue we’re addressing. |
M03150300 | 503 | Scheduled Maintenance | Currently the API is under maintenance. Please check our API Status for more details. |
M03150400 | 504 | Gateway Timeout | Your request has exceeded response time limit. If this persists, please check our API Status It might be an issue we’re addressing. |
Documentation
- Technical Overview
- vehicle identifiers v1