Solve
One-off solves
Post a full problem and get back a plan.
Routite API · Optimization API
The API gives TMS vendors, platforms and in-house teams the same GPU solver the console uses: post a problem, ask for a re-solve, get routes, diffs and reasons back.
A call, step by step
POST /v1/solve { "vehicles": [{ "id": "van-1", "depot": "d4", "capacity": [120] }], "stops": [{ "id": "s-214", "lat": 52.37, "lon": 4.90, "window": ["12:00", "14:00"], "demand": [3] }], "objective": ["lateness", "distance"] } → 202 Accepted · job_7f3a · poll or receive a webhook
Job result · job_7f3a
ExampleStop 01 · Capabilities
Solve
Post a full problem and get back a plan.
Re-solve
Send only the event; Routite re-solves from the current plan.
Diff
Each result lists moved stops and new ETAs.
Reasons
Machine-readable reasons per moved stop.
Async
Large problems run as jobs with a webhook when done.
Keys
Keys per environment and region, with usage reports.
Stop 02 · Data formats
| Format | Used for | Direction | Status |
|---|---|---|---|
| JSON | Problems, plans, diffs, reasons | In and out | In build |
| CSV | Bulk orders and history for replays | In | In build |
| GeoJSON | Routes and zones for maps | Out | In build |
| Webhooks | Plan ready, change approved, stop served | Out | In build |
| TMS and WMS connectors | Orders in, routes out | Both | Planned |
| Telematics feeds | GPS and vehicle status | In | Planned |
Stop 03 · How it works
A problem or an event, as JSON.
The job runs on cuOpt in Routite cloud.
Plan, diff and reasons, by webhook or polling.
Stop 04 · Specification
| Item | Detail | Status |
|---|---|---|
| Protocol | HTTPS, JSON, REST | In design |
| Auth | Scoped API keys; OAuth planned | In design |
| Limits | Up to 10,000 stops per problem | Design target |
| SDKs | Python and TypeScript | Planned |
Stop 05 · Place in the loop
The API is a branch off the loop: the same engine as Optimize, for teams that want to build their own console or embed routing in theirs.
Return leg Edge sends real arrival and service times back to Twin. ETA and demand models retrain on them, so tomorrow's first plan starts closer to reality.
Stop 06 · Questions
Design partners get the draft API first. Write to the engineering address on the contact page.
Pricing is by usage of solves and re-solves; see the pricing page. We do not publish prices yet.
Yes, with synthetic cities, planned for the first API release.
Stop 07 · Destination
Next step
A replay of one past day shows what this product would have done, with every assumption written down.