HTTP response codes

Service version: 1
Last edit: 2024.05.29
TomTom Orbis Maps

Important notes:

  • Orbis Maps Assets API is currently in public preview.
  • This API is powered by the TomTom Orbis Maps.
  • See the TomTom Orbis Maps documentation for more information on Orbis Maps.
  • See the Orbis Maps Assets API Migration page page for information on how to migrate and use the new Orbis Maps Assets API.
  • Use of the Orbis Maps Assets API requires an API Key with access rights to Assets API and, depending on the requested assets, Map Display API and/or Traffic API.


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


Meaning & possible causes


OK: the request has succeeded.


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.


Bad request: the server cannot process the request due to a client error (for example malformed syntax).


Forbidden: the server understands the request but refuses to authorize it.
The supplied API Key is not valid for this request - check your apps page.


Too Many Requests: too many requests were sent in a given amount of time for the supplied API Key.


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.


Service Not Found: the requested service is unknown.
Hint: Double-check the spelling of the request URL.