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



Service version: 1
Last edit: 2021.06.23

On this page


The Web Map Tile Service (WMTS) is the Open Geospatial Consortium (OGC)'s standard for delivering rectangular map tiles via RESTful web services. It consists of two key service calls: GetCapabilities and GetTile.


The "GetCapabilities" call documented here implements the 1.0.0 version of the WMTS standard. It returns an XML structure containing metadata on both the company hosting the service (in this case, TomTom) and the various layers that the service offers. That metadata is sufficient to allow calling systems to construct calls to Tomtom's Maps Tile API that retrieves individual raster map tiles for a given geographic extent, zoom level, and layer type.


Because the TomTom WMTS services follow the OGC WMTS specification, it is then easy to use these services via third party tools such as Esri's ArcGIS Online. While less flexible than the WMS API, WMTS "GetTile" calls are tailored for speed. They retrieve single map tiles and do not aggregate tiles in order to deliver a single composited map image.

Run this endpoint

You can easily run this and other endpoints.

  1. Go to the TomTom API Explorer page.
  2. Click an endpoint.
    1. Click Try it out.
    2. Enter/select all required parameter values and any optional parameter values.
    3. At the bottom of the form, click Execute.
  3. Review the Response.

▲ Return to top

Request data

HTTPS method: GET

Communication through both HTTP and HTTPS is supported.

URL format

For ease of viewing and identification:

  • Required constants and parameters are shown in bold text.
  • Optional parameters are shown in plain text.


curl command

curl -XGET ''

▲ Return to top

Request parameters

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

  • Required parameters must be used or the call will fail.
  • Optional parameters may be used.
  • If there is a default value that will be assumed when an optional parameter is not used, it is shown in the table.
Required parameters
Parameter Description
The base URL for calling TomTom services.
The version of the service to call.
Value: The current version is 1.
The authorization key for access to the API.
Value: Your valid API Key.
The version of the WMTS service.
Value: 1.0.0
Optional parameters
Note: There are no optional parameters in this endpoint.

HTTP Request headers

The following data table lists HTTP Request headers of particular interest to clients of the Maps WMTS API endpoint.

Required headers
Note: There are no required headers in this endpoint.
Optional headers
Header Description
Tracking-Id Specifies an identifier for the Request.
  • It can be used to trace a call.
  • The value must match the regular expression '^[a-zA-Z0-9-]{1,100}$'.
  • An example of the format that matches this regular expression is a UUID (e.g., 9ac68072-c7a4-11e8-a8d5-f2801f1b9fd1). For details check RFC 4122.
  • If specified, it is replicated in the Tracking-Id Response header.
Value: <string>

▲ Return to top

Response data

A full schema (XSD) for the Response is available from openGIS. The following XML code block is a partial example of a successful Response. For the meanings and use of the different elements, please refer to the schema.

Response body (XML)

<?xml version="1.0" encoding="UTF-8"?>
<Capabilities xmlns="" xmlns:ows="" xmlns:xlink="" xmlns:xsi="" xmlns:gml="" xsi:schemaLocation=""version="1.0.0">
    <ows:Title>TomTom Web Map Tile Service</ows:Title>
    <ows:ServiceType>OGC WMTS</ows:ServiceType>

    <ows:ProviderName>TomTom International B.V.</ows:ProviderName>
    <ows:ProviderSite xlink:href=""/>
      ( information for support of the service...)

    <ows:Operation name="GetCapabilities">
      (...metadata on the GetCapabilities call)
    <ows:Operation name="GetTile">
      (...metadata on the GetTile call)

    <!-- Basic Map -->
      <ows:Title>TomTom Map — Standard</ows:Title>
      <ows:WGS84BoundingBox crs="urn:ogc:def:crs:OGC:2:84">
        <ows:LowerCorner>-180 -85</ows:LowerCorner>
        <ows:UpperCorner>180 85</ows:UpperCorner>
      <Style isDefault="true">
      <ResourceURL format="image/png" template="{Style}/{TileMatrix}/{TileCol}/{TileRow}.png?key=apiKey" resourceType="tile"/>
      <ResourceURL format="image/png" template="{Style}/{TileMatrix}/{TileCol}/{TileRow}.png?key=apiKey" resourceType="tile"/>
      <ResourceURL format="image/png" template="{Style}/{TileMatrix}/{TileCol}/{TileRow}.png?key=apiKey" resourceType="tile"/>
      <ResourceURL format="image/png" template="{Style}/{TileMatrix}/{TileCol}/{TileRow}.png?key=apiKey" resourceType="tile"/>
      (...metadata on additional layers...)

          <ows:BoundingBox crs="urn:ogc:def:crs:EPSG:6.18:3:3857">
            <ows:LowerCorner>20037508.3428 -20037508.3428</ows:LowerCorner>
            <ows:UpperCorner>-20037508.3428 20037508.3428</ows:UpperCorner>
            <TopLeftCorner>-20037508.3428 20037508.3428</TopLeftCorner>
          (...metadata on further matrixes...)

  <ServiceMetadataURL xlink:href=""/>

▲ Return to top

Error Response

The Map Display API WMTS service for an invalid request returns a response body in plain text or JSON format. The plain text format is returned by default.
To have an error response returned in JSON format, application/json has to be specified in the Accept HTTP request header.

Plain text format
Malformed syntax

Error response field structure

Field Description
Main object of the error response.
One of a server-defined set of error codes.
A human-readable description of the error code.

Error response example

JSON format
      "detailedError" : {
        "code" : "BAD_REQUEST",
        "message" : "Malformed syntax"

▲ Return to top

HTTP response codes

Code Meaning and possible causes
200 OK
400 Bad request: Probably malformed syntax.
403 Unauthorized: The supplied API Key is not valid for this Request.
429 Too Many Requests: Too many requests were sent in a given amount of time for the supplied API Key.
500 Internal Server Error: There is a problem with the TomTom WMTS service.

HTTP Response headers

The following table lists HTTP Response headers of particular interest to clients of the Maps WMTS API endpoint.

Header Description
Access-Control-Allow-Origin The Maps WMTS API allows cross-origin resource sharing (CORS).
Value: *
Cache-Control Contains directives for a caching mechanism.
Value: public, max-age=<decimal number>
Content-Length Contains information about the size of the Response body.
Value: <decimal number>
Content-Type Indicates the media type of the resource returned.
Values: text/xml; charset=utf-8
Date Contains the date and time at which the message was originated.
Value: <http-date>
Tracking-Id An identifier for the Request.
  • If the Tracking-Id header was specified in the Request, it is replicated in the Response.
  • Otherwise, it is generated automatically by the service. For details check RFC 4122.
Value: <string>

▲ Return to top