Skip to main content
POST
Check a solve 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/solve.

problem
object
required

The problem: tasks, fleet, depots, relations, objective, travel.

Example:
options
null | object

Solve options.

Example:
plan
null | object

Warm start: the plan the search starts from instead of constructing from scratch (re-optimization). A result's plan goes in as it stands. See plan.routes[].locked_count for freezing a dispatched prefix.

A hint, not a guarantee: an unlocked stop that violates a hard constraint (e.g. capacity, skills, eligibility, limits.*, or a time window with no per_late_hour set) is left unassigned and the search reinserts it wherever it legitimately fits, or it surfaces in unassigned[] with a typed reason. On synchronous solve and stream, an infeasible locked stop is a 400. POST /v3/routing/runs checks the problem at submission, not the plan, so there the run ends failed with BAD_REQUEST instead. A pinned stop outside a locked_count prefix (a shipment leg whose other leg is inside counts as inside) is never a 400 or a failed run: one that cannot be served is in unassigned[] (see pinned).

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.