Skip to main content
POST
Create table (async)

Authorizations

Authorization
string
header
required

API key authentication. Include your API key in the Authorization header.

Body

application/json

Table Dto

coordinates
number<double>[][]
required

The coordinates this request will use, coordinates as [{lon},{lat}] values, in decimal degrees.

Minimum array length: 2
sources
integer<int32>[] | null

An array of index elements (0 <= integer < #coordinates) to use location with given index as source. Default is to use all.

destinations
integer<int32>[] | null

An array of index elements (0 <= integer < #coordinates) to use location with given index as destination. Default is to use all.

annotations
string[] | null

Return the requested table or tables in response. Can be ['duration'] (return the duration matrix, default) or ['duration', distance'] (return both the duration matrix and the distance matrix).

vehicleType
enum<string> | null

The vehicle type for which the table is requested

Available options:
CAR,
BIKE,
TRUCK,
ELECTRIC_CAR,
ELECTRIC_BIKE
engine
enum<string> | null

Routing data engine used to calculate distances/durations.

  • OSM: Open Street Map, traffic-unaware (default).
  • TOMTOM: TomTom map data with predictive traffic patterns. Use with departureTime and optionally interpolate.
  • TOMTOM_REAL_TIME: TomTom map data with real-time traffic. The departureTime field is ignored — every request uses the current time. Available on POST /route and POST /table/sync only (not on async /table or /route/batch). Live traffic is combined with historical traffic patterns by default; set includeTrafficPatterns: false for live traffic only.
  • GOOGLE: Google routing data (contact sales).
  • ANYMAP: Solvice's proprietary engine with advanced traffic modeling.
  • CUSTOM: Bring-your-own engine via custom integration.
Available options:
OSM,
TOMTOM,
GOOGLE,
ANYMAP,
CUSTOM,
TOMTOM_REAL_TIME
departureTime
string<date-time> | null

The departure time (ISO8601) for which you want to calculate the route. This will take into account predictive travel time based on TomTom data.

Example:

"2024-03-15T08:30:00.000Z"

interpolate
boolean | null

Enable linear interpolation between time slices for more accurate results based on departure time

exclude
enum<string>[] | null

Exclude certain road types from routing

Available options:
TOLL,
MOTORWAY,
FERRY,
TUNNEL,
BRIDGE
includeTrafficPatterns
boolean | null

TOMTOM_REAL_TIME only: combine live traffic with TomTom historical time-of-day traffic patterns (default true). Patterns improve estimates outside peak hours and cover roads without live traffic data. Set false to use live traffic only.

Response

Table created successfully

id
integer<int64>

Table id.

status
enum<string> | null

Table status (IN_PROGRESS, SUCCEEDED, FAILED).

Available options:
IN_PROGRESS,
AGGREGATING,
SUCCEEDED,
FAILED,
CREATING
errorMessage
string | null

Error message if the Cube failed.

hash
integer<int32> | null

Hash of the Cube request

nrOfSources
integer<int32> | null

Number of sources in the table

nrOfDestinations
integer<int32> | null

Number of destinations in the table

tableResponseId
integer<int64>

Table response id.

updatedAt
string | null

Last update time of the table.

createdAt
string | null

Creation time of the table.