List sprites versions
Purpose
- The list sprites versions endpoint functionality shows the user the available sprites versions and allows them to choose the one needed.
- It returns an array of sprite versions, along with URLs to services which allow retrieval of further listings of sprites.
- With the appropriate sprite version, users can list the specific sprites available for that version using the List sprites functionality.
Request data
HTTPS method: GET
- Constants and parameters enclosed in curly brackets
{}must be replaced with their values. - Please see the following Request parameters section with the required and optional parameters tables for their values. The generic request format is as follows.
URL format
https://{baseURL}/maps/orbis/assets/sprites?key={Your_API_Key}&apiVersion={API_Version}https://api.tomtom.com/maps/orbis/assets/sprites?key={Your_API_Key}&apiVersion=1curl 'https://api.tomtom.com/maps/orbis/assets/sprites?key={Your_API_Key}&apiVersion=1Request parameters
The following table describes the parameters that can be used in a request.
- Required parameters must be used or the call will fail.
- Parameters and values are case-sensitive.
- Optional parameters may be used.
| Required parameters | Description |
|---|---|
| The base URL for calling TomTom services. |
| The API version of the service to call. |
| An API Key valid for the requested service. |
Request headers
HTTP request headers are common in the Assets API service. For details, see HTTP request headers .
Response data
Successful response
For a single request, the service returns its response body in JSON format.
Response schema
{ "versions": [ { "version": "string", "url": "string" } ]}Response field structure
The following table describes JSON element fields that can appear in a response.
| Field | Description |
|---|---|
| The version of the chosen sprite. |
| The URL to the chosen sprite matching the |
Example
{ "versions": [ { "version": "0.0.0-0", "url": "https://api.tomtom.com/maps/orbis/assets/sprites/0.0.0-0?apiVersion=1&key={api_key}" } ]}Error response
Error response field structure
The following table describes JSON element fields that can appear in an error response.
| 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. |
Example
{ "detailedError" : { "code" : "BAD_REQUEST", "message" : "Invalid format of the api version." }}Response codes
HTTP response codes are common in the Assets API service. For details, see HTTP response codes .
Response headers
HTTP response headers are common in the Assets API service. For details, see HTTP response headers .