Skip to main content
GET
Retrieve a route
Fetch a route plan by its name. The name goes in the URL path. The lookup matches on name across all dates and returns matches newest first, so the first result is the most recent plan with that name. Results are paginated and use the same data array shape as List routes.
This endpoint doesn’t filter by date. If you reuse a route name on different days, check each result’s date, or use List routes with the date parameter.
Each route has two levels:
  • The plan (the top-level object) holds the plan’s status, depot, and totals across all vehicles.
  • planned_routes has one entry per vehicle, with that vehicle’s status, start_time, completion_time, time window, and its planned_jobs in delivery order (job_sequence, eta_time).
Jobs that couldn’t be placed on any vehicle are in the plan-level unplanned_jobs. The plan-level vehicle shows one of the plan’s vehicles; use planned_routes[].vehicle to see which vehicle drives which route. See Route status for what each status value means.

Authorizations

X-API-KEY
string
header
required

Your Detrack API key, from Integrations > API Key in the dashboard.

Path Parameters

name
string
required

Exact name of the route plan, URL-encoded.

Example:

"sample_run"

Query Parameters

page
integer
default:1

Page number.

limit
integer
default:25

Records per page. The API doesn't cap it, but keep it to 100 or fewer.

Response

Matching route plans.

data
object[]
total_count
integer
Example:

1