HTTP request headers
The following table describes HTTP request headers.
Note: There are no required request headers in Geofencing API endpoints.
Specifies an identifier for the request.
HTTP response headers
The following table describes HTTP response headers.
The Access-Control-Allow-Origin response header indicates whether the
response can be shared with the requesting code from the given origin.
The Connection general header controls whether or not the network
connection stays open after the current transaction finishes.
The Content-Encoding entity header is used to compress the media-type.
The Content-Length entity header indicates the size of the entity-body
in bytes that are sent to the recipient.
The Content-Type entity header is used to indicate the media type of the
The Date general header contains the date and time at which the message
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.
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.
An identifier for the request. A 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.