getTileServiceCapabilities

Last edit: 2026.11.04

Returns which optional methods the service implements. Call it before your map data component relies on one of them, such as delta updates.

Request data

HTTP method: `POST`

URL request format

1
https://{serviceURL}/getTileServiceCapabilities?apiKey={Your_API_Key}

serviceURL is your Smart Layer Tile Service endpoint, without /openapi.json.
Your_API_Key is a My.TomTom API key with NDS.Live services enabled.

Request body

This method takes no request body.

HTTP request headers

This method needs no request headers.

Response data

Response body

On success, the body is a zserio-encoded TileServiceCapabilitiesResponse object. Its capabilities field is a bitmask, TileServiceCapabilities. The service includes one flag for each optional method it implements. Your map data component reads the flags; it can’t change them. These flags cover the methods of this service:

Flag	The service implements
`GET_LAYER_BY_TILE_ID`	`getLayerByTileId`
`GET_HEADER_ONLY_BY_TILE_ID`	`getHeaderOnlyByTileId`
`GET_DELTA_LAYER_BY_TILE_ID`	`getDeltaLayerByTileId`
`GET_SINGLE_DATA_LAYER_BY_TILE_ID`	`getSingleDataLayerByTileId`

The bitmask also has flags for methods that this service doesn’t offer, such as the list variants. For example, the ADAS Road Model evaluation endpoint returns 1093 (0x0445), which includes exactly the four flags in the table. Code generated from the NDS.Live schema with zserio includes the flags by name.

HTTP status codes

Besides the codes below, any method can return the common errors, for example 401 for a missing API key.

Code	Meaning
`200`	OK. The response body holds the `TileServiceCapabilitiesResponse`.
`410`	Gone. The Smart Layer Tile Service is decommissioned. Ask the NDS.Live Registry for another service.
`500`	Internal server error.