Sorry, you need to enable JavaScript to visit this website.

HTTP response codes


Service version: 1
Last edit: 2019.09.18


The HTTP response codes in the following table describe data returned as a response from an API server after a RESTful request has been made. It includes success and failure codes and their descriptions.

Code Meaning and possible causes
200 OK
201 Created
206 Partial Content
400 Malformed request: Malformed syntax. Possible causes include: The requested syntax is not available.
400 Bad request: Parameters out of range. Possible causes include:
  • A Geofencing Report has been requested without a project for an object without a default project.
  • The range parameter is not in the 0,100000 value range.
  • The point parameter is missing its mandatory latitude or longitude or consists of more than three coordinates.
  • The provided project/fence/object is not linked to the requester's account or does not exist.
  • The provided latitude is not in the -90,90 value range.
  • The provided longitude is not in the -180,180 value range.
  • The provided altitude is not in the -500,15000 value range.
  • Wrong datetime format.
  • The timestamp is later than the current date.
  • The timestamp is earlier than or equal to the timestamp of the last position.
401 Unauthorized:
  • The supplied Admin Key is not valid for this request.
  • No Admin Key is supplied.
401 Unauthorized: Configuration not found.
  • The configuration does not exist in the database.
  • The user has not registered an Admin Key.
403 Forbidden: The supplied API Key is not valid for this request.
403 Forbidden: User can only register once.
500 Internal Server Error: There is a problem with the TomTom Geofencing API service.

▲ Return to top