Limits

V3 is in beta. General availability (GA) is planned for January 2027.

Overview

These limits apply to POST /v3/routing/solve, /v3/routing/evaluate and /v3/routing/suggest, and to POST /v3/routing/runs, which takes the solve body (see Async runs for what differs). Most are checked before any travel times are fetched, so an oversized request fails fast and is reported by POST /v3/routing/validate/* as well. A request over a count limit gets a 400 whose errors[] item has code limit_exceeded, the limit and the actual count your request has:

400 Bad Request

{
  "status": "BAD_REQUEST",
  "code": "invalid_request",
  "message": "the request has 10250 tasks (jobs + shipments); the maximum is 10000",
  "request_id": "req_5c1e8a3f9d02b746",
  "errors": [
    {
      "code": "limit_exceeded",
      "pointer": "/problem/jobs",
      "message": "the request has 10250 tasks (jobs + shipments); the maximum is 10000",
      "limit": 10000,
      "actual": 10250
    }
  ]
}

See Errors for the full error body.

Request

Limit	Value	When you exceed it
Body size	10 MiB, measured after decompression	`413`, code `payload_too_large`
Body compression	`Content-Encoding: gzip`, or none	`415`, code `unsupported_media_type`
Content type	`application/json`	`415`, code `unsupported_media_type`
Problems listed in one error response	100	The `message` says the list was cut; fix those and resend

Solve time

Limit	Value	When you exceed it
`options.time_limit_s` on solve	Default 150 ms plus 4 ms per task (tasks are jobs and shipments together). Maximum `60`. Fractions allowed; a value below `0.1` is raised to 100 ms	Above 60: `400`, item `limit_exceeded`, pointer `/options/time_limit_s`. Negative: `400`, item `out_of_range`
`options.time_limit_s` on an async run	Default 150 ms plus 4 ms per task. Maximum `3600`. Fractions allowed; a value below `0.1` is raised to 100 ms	Above 3600: `400`, item `limit_exceeded`, pointer `/options/time_limit_s`. Negative: `400`, item `out_of_range`
`options.time_limit_s` on suggest	Default `1`. Maximum `60`. Fractions allowed; a value below `0.1` is raised to 100 ms	Above 60: `400`, item `limit_exceeded`, pointer `/options/time_limit_s`. Negative: `400`, item `out_of_range`
`options.max_insertions` on suggest	Default `5`. Integer from `1` to `10`	`400`, pointer `/options/max_insertions`: item `out_of_range` for `0`, `limit_exceeded` above `10`

time_limit_s is a number of seconds, fractions allowed, and counts search time only. Fetching travel times and waiting for a free solver are not deducted from it, so the request takes somewhat longer than the budget you set; set your HTTP client timeout accordingly. The budget is a ceiling: a solve that starts from a plan, or that has one vehicle with one shift, can return earlier, and a busy service can shorten any solve’s search (see Performance). Evaluate takes no options because it does not search.

Problem size

Limit	Value	When you exceed it
Tasks: `jobs` plus `shipments`	10,000	`400`, item `limit_exceeded`, pointer `/problem/jobs` (`/problem/shipments` when there are no jobs)
Tasks on `POST /v3/routing/solve`	400. Submit a larger problem, up to the 10,000 above, as an async run: `POST /v3/routing/runs` takes the same body. Evaluate and suggest are not held to it	`400`, item `limit_exceeded`, pointer `/problem/jobs` (`/problem/shipments` when there are no jobs). `POST /v3/routing/validate/solve` reports it too
`vehicles`	2,000	`400`, item `limit_exceeded`, pointer `/problem/vehicles`
Stops in total	65,535, counting every job, both stops of every shipment, a start and an end for every vehicle shift, and the reload visits each shift may make	`400`, item `invalid_value`
Distinct locations	65,535	`400`, item `invalid_value`
Distinct locations with `travel.engine: "tomtom_real_time"`	100	`400`, item `limit_exceeded`, pointer `/problem/travel/engine`. This engine is not enabled yet, so a request within the cap gets the `403` described in Errors
`priority` on a job or shipment	Integer from `1` to `100,000,000,000,000` (1e14). The summed priority of the tasks left out is a 64-bit integer, and 1e14 on every one of 65,535 tasks still fits, so any mix of values adds up. To rank several goals with one field, see packing ranked goals	`400`, item `out_of_range`, pointer `/problem/jobs/{i}/priority`: a value below `1` or above `100000000000000`. A value beyond the 64-bit range fails to parse
`quotas`	65,535	`400`, item `limit_exceeded`, pointer `/problem/quotas`
Reloads at one depot in one shift	8. The solver plans no more than that. List more than one depot in `shifts[].reloads` to allow more reloads in a shift	A `plan` with more is a `400`, item `invalid_value`, pointer `/plan/routes/{i}/stops/{k}`. This is checked when the plan is matched to the problem, so `POST /v3/routing/validate/*` does not report it

Capacity, skills and tags

Limit	Value	When you exceed it
Capacity dimensions	4 distinct names, counted across every `pickup_load`, `delivery_load`, `capacity` and `initial_load` in the request	`400`, item `limit_exceeded`, pointer `/problem/vehicles`. The message lists the names found
Required skills	256 distinct combinations of skill `name` and `min_level` across all tasks. Skills that only vehicles have do not count	`400`, item `limit_exceeded`, pointer `/problem/jobs`
Task tags	256 distinct values across `jobs[].tags` and `shipments[].tags`. `serves_tags` and `preferred_tags` on the vehicle side do not count	`400`, item `limit_exceeded`, pointer `/problem/jobs`
`eligible_vehicles`	256 distinct vehicle sets across all tasks, after `allowed` and `excluded` are resolved. A set equal to the whole fleet does not count	`400`, item `limit_exceeded`, pointer `/problem/jobs`
Per-task `service_factors`	When any task sets it: vehicle shifts multiplied by task stops must not exceed 10,000,000	`400`, item `limit_exceeded`, pointer `/problem/jobs`

In a request with shipments and no jobs, the pointers shown as /problem/jobs in this table read /problem/shipments.

The four-dimension limit counts names, not vehicles. A typo such as wieght on one job counts as a dimension of its own. When you hit this limit unexpectedly, read the names in the error message.

Relations

Limit	Value	When you exceed it
Participants in one `synchronized` relation	8	`400`, item `limit_exceeded`, pointer `/problem/relations/{i}`
Tasks linked together across vehicles by `synchronized` and `time_lag` relations, and the `sequence` relations that join them	16 in one linked group	`400`, item `invalid_value`, pointer `/problem/relations`
Tasks in one `compatible_vehicles` relation	16, and at least 2	More than 16: `400`, item `limit_exceeded`, pointer `/problem/relations/{i}`. Fewer than 2: `400`, item `invalid_value`, pointer `/problem/relations/{i}/stops`
Tasks in one `all_or_none` relation	At least 2	`400`, item `invalid_value`, pointer `/problem/relations/{i}/stops`
`tag_order` relations	1 per request, with at least 2 groups	`400`

Values

Limit	Value	When you exceed it
Ids: `jobs[].id`, `shipments[].id`, a shipment leg’s own `pickup.id` and `delivery.id`, `vehicles[].id`, `vehicles[].shifts[].id`, `depots[].id` and `quotas[].id`	1 to 128 characters	`400`, item `invalid_value`, pointer to the `id`
`drop_cost`	At most 1,000,000,000	`400`, item `out_of_range`
`depots[].per_reload`	At most 1,000,000,000	`400`, item `out_of_range`
Service time after `service_factor` is applied	At most 100,000,000 seconds	`400`, item `out_of_range`
`speed_factor`, `service_factor` and `service_factors[].factor`	From 0.001 to 5	`400`, item `out_of_range`
`limits.max_distance_m` and `limits.max_route_duration_s`	At most 2,147,483,647	`400`, item `out_of_range`
`limits.max_leg_travel_s`	From 1 to 2,147,483,647	`400`, item `out_of_range`
Shift, time-window and break instants	Within 68 years (2,147,483,647 seconds) after the earliest shift start	An end past it is treated as open; a start past it is a `400`, item `invalid_value`

Prices

Amounts are in your currency. Prices have lower ceilings than drop_cost and depots[].per_reload. A ceiling applies to the field you send, not to what one stop ends up costing. A lateness rate times a long delay can exceed 21,474.83647 for a single stop; the solver charges it in full, and a priced window never makes a stop infeasible however high the price. A task with a drop_cost can still be left unassigned when serving it would cost at least its drop_cost.

Field	Maximum	When you exceed it
`preferences[].violation_cost`	21,474.83647 per entry, and 21,474.83647 for all entries of one task added together	`400`, item `out_of_range`
`assignment_costs[].cost`	21,474.83647 per entry	`400`, item `out_of_range`
`vehicles[].preferred_tags[].violation_cost`	21,474.83647 per entry, and 21,474.83647 for all entries of one vehicle added together	`400`, item `out_of_range`
`target.per_late_hour`	21,474.83647	`400`, item `out_of_range`
`time_windows[].choice_cost`	21,474.83647	`400`, item `invalid_value`, pointer to the task’s `time_windows`
`time_windows[].per_late_hour`	1,288,490	`400`, item `out_of_range`
`objective.per_late_hour`	1,288,490	`400`, item `out_of_range`
`objective.per_delay_workday`	21,474.83647 for the rate itself, and for the rate times the number of workdays after the earliest	`400`, item `out_of_range`
`per_travel_km` in `objective.costs`, `vehicles[].costs` or `shifts[].costs`	21,474,836	`400`, item `out_of_range`
`per_route_hour`, `per_wait_hour`, `per_drive_hour` and `per_overtime_hour`, at any of the three levels	77,309,411	`400`, item `out_of_range`
`per_route`, at any of the three levels	1,000,000,000	`400`, item `out_of_range`
`per_used_vehicle`, in `objective.costs` or `vehicles[].costs`	1,000,000,000	`400`, item `out_of_range`

For a rule that must always hold, use the hard field and not a high price: eligible_vehicles in place of a large violation_cost, and a time window with no lateness price in place of a large lateness rate. See Constraints.

Rate limits

Requests are also rate limited by the API gateway. A request over the rate limit is rejected with 429, and that response does not use the routing error body: see 429 Too Many Requests. The x-ratelimit-limit and x-ratelimit-remaining response headers are described in Authentication. When the service is at capacity it answers 503 with a Retry-After header. See Errors.

Errors

The error body and every code.

Performance

Choosing a time limit for your problem size.

Platform

Routing API

Overview

Request

Solve time

Problem size

Capacity, skills and tags

Relations

Values

Prices

Rate limits

Errors

Performance