Analysis List
Purpose
Send a GET request to return an analysis list.
The list is paginated and always sorted by creation time, newest first. It covers every analysis type.
Request data
HTTPS Method: GET
For ease of viewing and identification:
- 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://api.tomtom.com/origindestination/1/analysis?key={Your_API_Key}&page={page}&limit={limit}&name={name}&statuses={statuses}&types={types}&analysisVersion={analysisVersion}&favoriteOnly={favoriteOnly}&archivedOnly={archivedOnly}Example
https://api.tomtom.com/origindestination/1/analysis?page=1&limit=15&key={Your_API_Key}Request parameters
Required parameters | Description |
|---|---|
| Authorization key for access to the API. Value: Your valid API Key. |
Optional parameters | Description |
|---|---|
| Number of the page returned in the response. Pages are numbered from 1. Default value: |
| Number of analyses per page. Default value: |
| Free text search. An analysis matches when the value is contained in its Default value: none. Without it the list is not filtered by name. |
| Comma-separated list of job statuses to return. Default value: all statuses. |
| Comma-separated list of analysis types to return. Default value: all types. Possible values:
|
| Version of the analyses to return. Default value: none. Without it the list is not filtered by version. |
| When Default value: |
| Selects between archived and non-archived analyses; the two sets are never mixed. When
Default value: |
Response data
Response Example
Here is an example showing the correct response.
{ "analysisInfos": [ { "id": "1337", "name": "Example analysis", "type": "SELECTED_LINK", "analysisVersion": 2, "status": "ENDED", "currentProgress": 100, "estimatedDuration": null, "creationTime": "2026-07-18T07:39Z", "startAnalysisTime": "2026-07-18T07:52Z", "endAnalysisTime": "2026-07-18T08:12Z", "timeDefinition": { "dateRanges": [ { "startDate": "2026-06-01", "endDate": "2026-06-30", "exclusions": ["2026-06-02"], "daysOfWeek": ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY"] } ], "timeRanges": [ { "startTime": "00:00", "endTime": "00:00" } ], "zoneId": "Europe/Warsaw" } } ], "numberOfAllAnalyses": "1", "numberOfPages": 1}Response structure
Field | Description |
|---|---|
| List of analysis descriptions for the requested page. |
| Number of analyses matching the request across all pages, not the number of analyses in this response. |
| Number of pages for the provided parameters. |
AnalysisInfo structure
Field | Description |
|---|---|
| Analysis number id. |
| Job name, given for the user’s convenience. |
| Analysis type. One of the following values:
|
| Version of the analysis. Not returned for analyses created before versioning was introduced. |
| Job status. One of the following values:
|
| Current value of the job progress (0-100). |
| Estimated duration of the calculation, in seconds. Produced for Flow Matrix analyses only;
|
| Job creation time in |
| Date and time start of the analysis in |
| Date and time end of the analysis in |
| Time definition of the analysis. |
| Time zone as a
TZ database name. For example |
| List of date ranges of the analysis. |
| List of time ranges of the analysis. |
| Whether the analysis is marked as favorite. Returned only when the request contains the
|
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 |
| Days of the week the analysis covers inside this date range. Returned only when the analysis was created with it. Allowed values:
|
| Date range name. Given for the user’s convenience.
Value: A date range name. For example: |
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.
A request that matches no analysis is not an error: the response is a 200 with an empty
analysisInfos list.
Response codes
Code | Meaning & possible causes |
|---|---|
| OK |
| Bad Request |
| Unauthorized |
| Forbidden |
| Not Found |