Get Transport Route
Get Transport Route
Retrieve a specific transport route by ID, including all sections, distances, and emissions
GET
Get Transport Route
Get Transport Route
Retrieve a transport route by its unique identifier. The response includes all sections (legs), the calculated distance per section with the method used to compute it, and the CO2e emissions per section.Request
Authentication
Supports both authentication methods:Your API key (use this or
Authorization)Example: sk_live_1234567890abcdefBearer JWT token (use this or
x-api-key)Example: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...Headers
Your organization UUIDExample:
a8315ef3-dd50-43f8-b7ce-d839e68d51faPath Parameters
The unique identifier (UUID) of the transport routeExample:
010ed3b6-b513-40f3-b9fe-0f0a338d9274Response
Route Fields
Unique identifier (UUID)
Optional route name
Date of transport (YYYY-MM-DD).
null if not setAmount transported (max 10 digits, 3 decimal places)
Optional supplier name
downstream (outbound — goods sent to customers) or upstream (inbound — goods received from suppliers)Recurrence:
once, weekly, monthlyMeasurement unit for the quantity transported
Total CO2-equivalent emissions in kg across all sections.
null if no impacts have been calculated yetRoute-level emissions summary:
[{"value": 245.67, "gas": "co2e", "unit_name": "kgCO2e"}]Route status:
pending (awaiting calculation), active (calculated), error (calculation failed)ID of the uploaded file if this route was created via bulk upload
List of transport sections (legs). See Section Fields below
ISO 8601 creation timestamp
ISO 8601 last-update timestamp
Section Fields
Section UUID
Sequence number within the route (1-based)
road, air, maritime, rail, or do_not_knowSub-type for road transport:
car, truck, motorbike, bicycle, electric_kick_scooterWhether the vehicle is electric
Whether the cargo is refrigerated
Additional detail used for emission factor selection (e.g. distance band or weight class)
Origin location address
Destination location address
Calculated or user-provided distance in kilometers
Distance override provided directly by the user (max 7 digits, 2 decimal places). Present when
distance_manual is truetrue when the distance was provided manually via kms_manual instead of being auto-calculatedMethod used to calculate the distance. See Distance Calculation Methods for all values
Section status:
pending, active, errorCurrent processing step:
geocoding, impact_calculation, completedList of error messages when
status is errorCO2e emissions for this section:
[{"value": 12.34, "gas": "co2e", "unit_name": "kgCO2e"}]Distance Calculation Methods
Thekms_source field tells you exactly how the distance for a section was determined:
| Value | Transport type | Description |
|---|---|---|
cerdi_sea_distance | maritime | Country-pair formula from the CERDI dataset: sea route between main ports + capital-to-port land legs for both countries |
searoute_sea_distance | maritime | Navigable-water graph for same-country sea routes (e.g. mainland Spain → Canary Islands) |
haversine_sea_distance | maritime | Haversine great-circle fallback for same-country maritime when the graph is unavailable |
haversine_formula | air | Great-circle distance between geocoded coordinates |
google_maps_distance_matrix_v1 | road / rail | Google Maps Distance Matrix API |
aws_location_route_matrix | road / rail | AWS Location Service (alternative to Google Maps) |
default | maritime / road | Hardcoded fallback: 500 km for same-country maritime, 3 km for same-place road |
manual | any | User provided the distance directly via kms_manual |
null | any | Not available — section pre-dates geocoding, or geocoding failed |
Why does a Spain → Syria maritime section show 4626 km?CERDI is a country-level dataset. The 4626 km is composed of three fixed values for the
ESP → SYR pair:- 3761 km — sea route between Spain’s and Syria’s representative ports
- 655 km — land distance from Madrid (Spain’s capital) to its main sea port
- 210 km — land distance from Damascus (Syria’s capital) to its main sea port
kms_manual when creating the section.Example
Successful Response
Common Errors
401 Unauthorized
Cause: Missing or invalid API key / JWT token403 Forbidden
Cause: The authenticated user is not a member of the organization404 Not Found
Cause: Route ID does not exist or belongs to a different organizationRelated Endpoints
List Transport Routes
Retrieve all transport routes with filtering and pagination
Create Transport Route
Create a new transport route with sections
Update Transport Route
Modify a transport route and its sections
Transport Overview
Full data model and distance calculation reference

