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

Status for all locations

Service version: 1.0
Last edit: 2020.06.23

On this page


The Status for all locations endpoint provides Live Traffic status for all locations created by users from your organization.

▲ Return to top

Request data


URL format<Your_API_Key>

curl command format

curl '<Your_API_Key>'

Request parameters

The following table describes the parameters that can be used in a Request.

  • Required parameters must be used or the call will fail.
  • Optional parameters, which are highlighted with [square brackets], may be used.
Required parameters
Parameter Description
Base URL for calling the API.
Service version.
Value: The current value is v1.
An API Key valid for the requested service.
Value: Your valid API Key.
integer (query)
The page number.
Value: An integer
integer (query)
The size.
Value: An integer.
Optional parameters
The ISO Country code.
Value: A string.
Email of the event reporter
Value: A string.
The sort facility.
Value: lastModifiedAt;desc or lastModifiedAt;asc

Request Headers

Header Description
Optional. Enables response compression.
Value: gzip

▲ Return to top

Response data

Response body

For illustrative purposes the example below is neatly indented and includes all possible Response fields.
  • Actual Responses are more compact and the fields present will vary based on the result type and the data available.
  • See the following Response field documentation for more information.
When requesting JSON output, the Response has the following structure:
  "entities": [
      "locationId": 0,
      "liveStatusAB": "string",
      "liveStatusBA": "string",
      "overlapPercentageAB": 0,
      "overlapPercentageBA": 0,
      "lastModifiedAt": "2020-06-03T17:20:32.575Z"
  "commonFilters": {
    "additionalProp1": {},
    "additionalProp2": {},
    "additionalProp3": {}
  "domainFilters": {
    "additionalProp1": {},
    "additionalProp2": {},
    "additionalProp3": {}

▲ Return to top

Response fields

The following table describes all of the fields that can appear in a Response. Fields are listed by the Response section they belong to and in the order that they appear in the Response.

Primary fields
Field Description
A list of location items.
Field Description
The list of common filters applied.
The list of additional fiters applied.
Field Description
The location id.
Live Traffic status for a positive direction. See: Live Status - explanation.
Live Traffic status for a negative direction. See: Live Status - explanation.
Value from 0 to 100. Describe what percentage of the location length, in positive direction, is exposed as a incident in TomTom Live Traffic service
Value from 0 to 100. Describe what percentage of the location length, in negative direction, is exposed as a incident in TomTom Live Traffic service
The date of the last status modification.

▲ Return to top

Live Status - explanation

  • ACCEPTED: The whole geometry is ACCEPTED by the Traffic Fusion System and is visible in the output.
  • PARTIALLY_ACCEPTED: The part of geometry is ACCEPTED by the Traffic Fusion System and is visible in the output.
  • REJECTED: The whole geometry is rejected by the Traffic Fusion System and is visible in the output.
  • MATCHING_ERROR, INVALID, UNKNOWN: This should not happen; please contact
  • INITIAL, SENT: Technical statuses; the Road Event Reporter did not receive a status from the Live Traffic Fusion.
  • PENDING: The location is loaded by Live Traffic Fusion; waiting on the defined date to be published.
  • PAST_DUE: The location is no longer valid.

▲ Return to top

HTTP Response Codes

The following table contains Response Codes signifying successful and failed requests to an API server. (Choose which Response Codes are used in this endpoint from the following table. Delete the ones not used, and add new ones if needed.)

Successful and failed Response codes

Code Meaning and possible causes
200 OK
206 Partial Content
400 Malformed request: The requested syntax is not available.
400 Bad request: Parameters out of range.
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.
429 Too Many Requests: The API key is over QPS (Queries per second).
500 Internal Server Error: There is a problem with the TomTom Road Event Reporter Enterprise API service.

▲ Return to top

Response headers

The following table contains Response headers sent back from an API server.

Header Description
Access-Control-Allow-Origin The Access-Control-Allow-Origin response header indicates whether the Response can be shared with the requesting code from the given origin.
Value: *
Connection The Connection general header controls whether or not the network connection stays open after the current transaction finishes.
Value: keep-alive
Content-Encoding The Content-Encoding entity header is used to compress the media-type.
Value: gzip
Content-Length The Content-Length entity header indicates the size of the entity-body in bytes that are sent to the recipient.
Value: Content-Length
Content-Type The Content-Type entity header is used to indicate the media type of the resource.
Value: application/json;charset=UTF-8
Date The Date general header contains the date and time at which the message was originated.
Value: Date
Strict-Transport-Security The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP.
Value: max-age=<expire-time>& includeSubDomains
Vary The Vary HTTP response header determines how to match future request headers to decide whether a cached Response can be used rather than requesting a fresh one from the origin server.
Value: A comma-separated list of header names.
Tracking-ID An identifier for the Request. An unique identifier used by TomTom to identify and log a specific client Request and trace it back for support purposes. It is only meant to be used for support and does not involve tracking of you or your users in any form. If the Tracking-ID header was specified, it is replicated in the Response. Otherwise, it is generated automatically by the service.
Value: string

▲ Return to Top