Analysis List
Purpose
Send a GET request to return an analysis list.
Request data
HTTPS Method: GET
For ease of viewing and identification:
- 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.
Format
https://{baseURL}/origindestination/{versionNumber}/analysis?key={Your_API_Key}&page={page}&limit={limit}&name={name}
Example
https://api.tomtom.com/origindestination/1/analysis?page=1&limit=15&key={Your_API_Key}
Request parameters
Required parameters | Description |
---|---|
| The base URL for calling TomTom services. Value: |
| Version of the service to call. Value: The current value is |
| Authorization key for access to the API. Value: Your valid API Key. |
Optional parameters | Description |
---|---|
| Number of page returned in the response. |
| Number of analyses per page. |
| Filter analyses by name containing given value. |
Response data
Response Example
Here is an example showing the correct response.
1{2 "analysisInfos": [3 {4 "id": "1337",5 "name": "Example analysis",6 "owner": "user@example.com",7 "status": "ENDED",8 "currentProgress": 100,9 "creationTime": "2019-07-18T07:39Z",10 "startAnalysisTime": "2019-07-18T07:52Z",11 "startAnalysisTime": "2019-07-18T08:12Z",12 "tripsCounted": 12345,13 "timeDefinition": {14 "dateRanges": [15 {16 "startDate": "2018-12-01",17 "endDate": "2018-12-31",18 "exclusions": ["2018-12-02"]19 }20 ],21 "timeRanges": [22 {23 "startTime": "00:00",24 "endTime": "00:00"25 }26 ],27 "zoneId": "Europe/Warsaw",28 "daysOfWeek": ["WEDNESDAY", "FRIDAY", "MONDAY", "TUESDAY", "THURSDAY"]29 }30 }31 ],32 "numberOfAllAnalyses": 1,33 "numberOfPages": 134}
Response structure
Field | Description |
---|---|
| List of analysis descriptions. |
| Number of all analyses in the response. |
| Number of pages for the provided parameters. |
AnalysisInfo structure
Field | Description |
---|---|
| Analysis number id. |
| Job name, given for the user’s convenience. |
| Email of the analysis' owner. |
| Job status. One of the following values:
|
| Current value of the job progress (0-100). |
| Job creation time in |
| Time definition of the analysis. |
| Time zone as a TZ database name. For example "Europe/Amsterdam" or "UTC" |
| Days of the week of the analysis. Allowed values:
|
| List of date ranges of the analysis. |
| List of time ranges of the analysis. |
| How many trips were counted. Updates when the analysis is in progress. |
| Date and time start of the analysis in the format:
|
| Date and time end of the analysis in the format:
|
Date range format
Field | Description |
---|---|
| Start date of the date range in |
| End date of the date range in |
| List of dates to exclude from a given range in |
| Date range name. Given for the user's convenience. Value: A date range name. For example: "Last working week of January". |
Time range format
Field | Description |
---|---|
| Start time of the time range in |
| End time of the time range in |
Errors
If there is an error in the supplied parameters or any other internal problem, an error response is generated in the requested format.
Response codes
Code | Meaning & possible causes |
---|---|
| OK |
| Bad Request |
| Unauthorized |
| Forbidden |
| Not Found |