Skip to main content
POST
Check a suggest request without running it
V3 is in beta. General availability (GA) is planned for 1 December 2026.

Authorizations

Authorization
string
header
required

Body

application/json

Request body for POST /v3/routing/suggest.

The same body as POST /v3/routing/evaluate, plus optional options. Given the committed plan over problem, ranks the feasible insertion positions for every task of problem that is not in plan — the tasks a solve would place and an evaluate would report as unassigned. Each task (or unit — a shipment, or tasks tied by one sequence/same_vehicle/ same_day/same_route relation) is ranked independently against the same committed plan; the plan is never modified.

plan
object
required

The committed plan. Never modified, never reordered. On suggest, locked_count keeps insertions after a route's dispatched prefix.

problem
object
required

Problem definition — identical to POST /v3/routing/solve. Every task of it that is not in plan is a task to place.

Example:
options
null | object

Suggest options. Absent: the defaults.

Example:

Response

The request passed every check made before travel times are fetched. warnings lists the advisories the real call would return that need no travel data: an options.time_limit_s below the 0.1 s floor (time_limit_raised), an option the travel engine makes inert, or plan flags evaluate ignores (no_effect).

The 200 body of POST /v3/routing/validate/{solve,evaluate,suggest}: the request passed every check a real call runs before the matrix fetch.

valid
boolean
required

Always true: an invalid request gets a 400 instead.

warnings
object[]
required

The advisories the real call would return in its own warnings[], as far as they need no travel data: an options.time_limit_s below the floor, an option that has no effect with the request's travel engine, plan flags evaluate ignores. Empty when there are none.