Sign in
plan

Plan Day Routes

Driving legs between one plan day's geocoded activities, in entry order.

Days are addressed by their ULID id, never an index: validation inserts derived days and reorders dated ones, so index positions differ between the stored plan and the validated view clients hold from GET /plans.

get/trips/{trip_id}/plans/{plan_id}/routes/{day_id}

Path parameters

trip_idstring required
plan_idstring uuid required
day_idstring required

Response

Successful Response

total_secondsinteger
total_metersinteger

Changes

Changed in 1 of the 22 revisions of this API.1