Get optimization result
Retrieve the optimization result for a completed job.
Call this endpoint once GET /planner/jobs/{job_id} returns status succeeded or not_drivable.
A succeeded result contains route sections with charging stop details (poi_summary) and candidate charging stations (poi_list). When status is not_drivable, the not_drivable_reason field explains why the route is not feasible.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Optimization identifier returned by POST /planner/v2.
Query Parameters
Tenant ID
Response
Successful Response
Response body for GET /planner/optimizations/{optimization_id}/result.
Optimization identifier.
Tour identifier.
Job lifecycle status; a result is available for succeeded or not_drivable.
queued, running, succeeded, not_drivable, failed, canceled Starting battery level (0-1).
Battery level at the end of the tour (0-1).
Route feasibility result: Driveable or not_drivable. See status for job lifecycle.
Route sections with charging stop details. May contain more sections than the request if charging stops were inserted.
Charging stations considered as candidates along the route.
Charging station filter criteria applied to this optimization.
Optimal departure time (ISO-8601) for reaching all time windows, if applicable.
Whether all time windows could be reached: 'True', 'False', or 'Not considered'.
All charging stations found within the route corridor, before the optimizer narrowed them down to the selected stops. Null for results created before this field was introduced.
Reason why the route is not drivable.
Advisory notes about this result that a dispatcher should check before dispatching — for example a custom search corridor, or a battery level that drops below the advisory minimum state of charge. Null when there is nothing to flag.