/cube
Request a time-dependent 3D distance matrix (cube) asynchronously. Returns a cube ID to poll status via /cube/ and fetch results via /cube//response. Use /cube//progress for progress on large matrices.
Documentation Index
Fetch the complete documentation index at: https://maps.solvice.io/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API key authentication. Include your API key in the Authorization header.
Body
Cube Dto
The coordinates this request will use, coordinates as [{lon},{lat}] values, in decimal degrees.
2An array of index elements (0 <= integer < #coordinates) to use location with given index as source. Default is to use all.
An array of index elements (0 <= integer < #coordinates) to use location with given index as destination. Default is to use all.
The vehicle type for which the table is requested
CAR, BIKE, TRUCK, ELECTRIC_CAR, ELECTRIC_BIKE The date for which you want to calculate the cube. This will take into account predictive travel time based on TomTom data. Format YYYY-MM-DD. Default is current date.
"2022-03-10T00:00:00.000Z"
Specifies the type of response to return. Currently only 'matrix' is supported (returns travel time matrices for each time slice).
Response
OK
Cube id.
Cube status (IN_PROGRESS, SUCCEEDED, FAILED).
IN_PROGRESS, AGGREGATING, SUCCEEDED, FAILED, CREATING Error message if the Cube failed.
Type of the Cube response, e.g., 'coefficients'.
Hash of the Cube request
Cube response id.
Last update time of the Cube.
Creation time of the Cube.