HTTP response codes
Important notes:
- This TomTom Orbis API is in public preview.
- This API is powered by the TomTom Orbis Maps.
- See the TomTom Orbis Maps documentation for more information.
Purpose
The HTTP response codes in the following table describe data returned as a response from an API server after a request has been made. It includes success and failure codes and their descriptions.
HTTP response codes
| Code | Meaning & possible causes |
|---|---|
| 200 | OK: the request has succeeded. |
| 304 | Not modified: there is no need to retransmit the requested resources. In the case of this API, this happens when the request is conditional and uses an If-None-Match header. |
| 400 | Bad request: the server cannot process the request due to a client error (for example malformed syntax). |
| 403 | Forbidden: the server understands the request but refuses to authorize it. |
| 429 | Too Many Requests: too many requests were sent in a given amount of time for the supplied API Key. |
| 500 | Internal Server Error: the server encountered an unexpected condition that prevented it from fulfilling the request. There is a problem with the services, Contact us. |
596 | Service Not Found: the requested service is unknown. |