List current options

Service version: 1
Last edit: 2022.07.21

Purpose

This endpoint is used to list account and privacy settings.

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

GET
Request example
https://{baseURL}/locationHistory/{versionNumber}/settings?key={Your_API_Key}&adminKey={Your_Admin_Key}

curl command format

GET
Request curl command
curl 'https://{baseURL}/locationHistory/{versionNumber}/settings?key={Your_API_Key}&adminKey={Your_Admin_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 may be used.
  • The order of request parameters is not important.

Note: There are no optional parameters in this endpoint.

Required parametersDescription
baseURL
string
The base URL for calling the API.
Value: api.tomtom.com
versionNumber
string
Service version.
Value: 1
key
string
An API Key valid for the requested service.
Value: Your API Key
adminKey
string
An Admin Key valid for the provided API Key.
Value: Your valid Admin Key.

Response data

Response body

The following JSON code block demonstrates a successful response from the API server.

Response body - JSON
1{
2 "accountSettings": {
3 "maxObjects": <number>
4 },
5 "privacySettings": {
6 "consentForStoringObjectsPositionsHistory": true/false,
7 "deleteAllHistoryBefore": "ISO8601_timestamp",
8 "deleteAllHistoryBeforeStatus": "&lt;string&gt;"
9 }
10}

Response fields

The following table describes all of the fields that can appear in a response.

Primary fields
FieldDescription
accountSettings
object
A collection of account settings.
privacySettings
object
A collection of settings that consists of information about privacy. By default historical data is not stored - permissions must be granted by the user.
accountSettings object
FieldDescription
maxObjects
integer
Maximum number of allowed objects in configuration.
privacySettings object
FieldDescription
consentForStoringObjectsPositionsHistory
boolean
Setting that allows the service to store sensitive, historical data in the Geofencing service. This field is shared between the Geofencing and Location History API.
Value: false
deleteAllHistoryBefore
timestamp
The date before all historical data will be cleared. If there was no request for the deletion of history, this field will not be presented. This field is shared between the Geofencing and Location History API.
Value: ISO8601 timestamp
deleteAllHistoryBeforeStatus
string
The status of the process of deletion. PROCESSING means that historical data is in a processing state. DELETED informs about the end of the delete process. If there was no request for the deletion of history, this field will not be presented. This field is shared between the Geofencing and Location History API.
Value: PROCESSING/DELETED

Response codes

CodeMeaning & possible causes
200OK
400Bad request:
  • Key missing.
  • Admin Key missing.
403Forbidden:Provided Admin Key is invalid.

Example

Request URL

GET
Request example
https://baseURL/locationHistory/1/settings?key={Your_API_Key}&adminKey={Your_Admin_Key}

Response body

Response body - JSON
1{
2 "accountSettings": {
3 "maxObjects": 1000
4 },
5 "privacySettings": {
6 "consentForStoringObjectsPositionsHistory": true,
7 "deleteAllHistoryBefore": "2019-07-10T12:30:00.000+00:00",
8 "deleteAllHistoryBeforeStatus": "DELETED"
9 }
10}