NavigationArrivalRequest

All fields are optional in the API — the handler is fail-open: missing or zero coordinates are silently dropped (204), never a 400. The documented fields below are the canonical set the client should send.

dest_latnumber<double>

The pin the user routed to.

dest_lngnumber<double>

final_latnumber<double>

Navigator's final position.

final_lngnumber<double>

profilestring

Driving is the default for anything else.

Possible values: [driving, foot, bicycle]

route_distance_minteger

Planned route distance.

route_duration_sinteger

Planned (computed) route duration at request time.

reroutedboolean

True if the trip was rerouted mid-navigation.

arrivedboolean

False = give-up (navigation abandoned before arrival).

Default value: true

origin_latnumber<double>

Trip origin — required for the traffic-sample capture.

origin_lngnumber<double>

shapestring

Polyline6 of the planned/driven route (optional).

started_atstring<date-time>

Trip start (RFC3339) — used when achieved_duration_s is absent.

arrived_atstring<date-time>

Trip end (RFC3339).

achieved_duration_sinteger

Actual elapsed trip time; preferred over the timestamps.

NavigationArrivalRequest

{
  "dest_lat": 0,
  "dest_lng": 0,
  "final_lat": 0,
  "final_lng": 0,
  "profile": "driving",
  "route_distance_m": 0,
  "route_duration_s": 0,
  "rerouted": true,
  "arrived": true,
  "origin_lat": 0,
  "origin_lng": 0,
  "shape": "string",
  "started_at": "2024-07-29T15:51:28.071Z",
  "arrived_at": "2024-07-29T15:51:28.071Z",
  "achieved_duration_s": 0
}