How is the route optimization API billed?

Per stop, prepaid: you buy a pack (2,000, 10,000, 50,000 or 250,000 stops) and every stop sent in a call uses 1 stop from your balance. There is no subscription or commitment, and stops never expire.

What happens if a call fails?

A call that fails (an address that cannot be geocoded, an engine error) is not charged: your stop balance is restored.

Do I need an Otiggo account to use the API?

No. You can buy a pack with just an email address: the API key is emailed to you after payment. Otiggo customers manage their keys and balance from Settings → API in the web app.

How many stops can I send per call?

Between 2 and 200 stops per call. Each stop is described by GPS coordinates or by a full address (street, postal code, city), with an optional deadline and service time.

Which constraints does the API handle?

The start point, an optional return point, the departure time, per-stop deadlines (late stops are flagged in the response), per-stop service time and toll avoidance. The response contains the optimized order, distance, duration and estimated arrival times.

Can I use the API from an AI assistant (MCP)?

Yes. Otiggo hosts an MCP server at https://app.otiggo.com/mcp: Claude Code, Cursor or any compatible MCP client can call optimize_route and get_balance with your API key. A free test key (10 stops per call, GPS coordinates) lets you try it without spending stops; a live key spends 1 stop per stop sent, like the API.

Where is the documentation?

The documentation (request format, response, error codes and a curl example) is at www.otiggo.com/developers/en, alongside pack purchase.

Otiggo API

Route optimization API for delivery

Otiggo's optimization engine, available from your own software. Prepaid per stop, from €0.012 to €0.050, no subscription.

One request, the best order

Your stops in, the visiting order, distance and duration out.

Estimated arrival times

A timestamped schedule, plus the stops that would miss their deadline.

Addresses or GPS coordinates

Addresses are geocoded for you; you can also send latitude and longitude.

No Otiggo account required

Buy a pack with your email and your API key is sent to you after payment.

What is a route optimization API?

A route optimization API takes a list of stops and returns the visiting order that cuts distance and drive time — the classic travelling-salesman problem, extended with delivery constraints (deadlines, service times, start and return to the depot). You send your stops and the API returns the ordered route with estimated arrival times.

It is built for TMS vendors, e-commerce businesses that deliver in-house, courier platforms and any engineering team that wants optimized routes without building and running a routing engine.

It is the engine behind the Otiggo app, exposed as a single route, with no Otiggo account required and no subscription: you pay for the stops you optimize.

Route optimization API for developers

Add delivery route optimization to your app, TMS, e-commerce platform or delivery software. Send a list of stops to the Otiggo REST API and get back the optimized visiting order, distance, estimated duration and arrival times.

The API accepts addresses or GPS coordinates and handles deadlines, service times, the start point, return to the depot and toll avoidance. It solves the stop order for one vehicle (a TSP problem); for a fleet, make one call per vehicle route.

Developer documentation

PRICING

Pay per stop — the more you buy, the less it costs

1 stop sent = 1 stop used. Stops never expire and a failed call is not charged.

2,000 stops

€99

€0.050 / stop

Integrated in minutes

One route, a key in the Authorization header, JSON responses.

1
Buy a pack
With your email, or from Settings → API if you are an Otiggo customer.
2
Receive your API key
It is emailed to you after payment; you can revoke it at any time.
3
Send your stops
One POST call with the start point and 2 to 200 stops, as addresses or coordinates.
4
Get the optimized route
Visiting order, distance, duration, arrival times and late stops.

Request

curl https://app.otiggo.com/api/v1/optimize \
  -H "Authorization: Bearer otg_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "start": { "street": "12 rue de la Paix", "postalCode": "75002", "city": "Paris" },
    "stops": [
      { "id": "A", "latitude": 48.87, "longitude": 2.30, "deadline": "10:30" },
      { "id": "B", "street": "5 avenue Foch", "postalCode": "75116", "city": "Paris" },
      { "id": "C", "latitude": 48.84, "longitude": 2.37 }
    ]
  }'

Response

{
  "order": ["B", "A", "C"],
  "totalDistanceKm": 11.2,
  "estimatedTimeMin": 54,
  "schedule": [{ "colisId": "B", "arrivee": "2026-10-20T05:41:00Z" }, …],
  "lateStops": null,
  "stopsCharged": 3,
  "stopsBalance": 1997
}

Full documentation, error codes and formats: Route optimization API documentation

AI ASSISTANTS

An MCP server for your AI assistants

Claude Code, Cursor or any MCP client can optimize your routes directly, using the same API key.

What the assistant can do

optimize_route: orders 2 to 200 stops (coordinates or addresses), with deadlines, service times and a return point.
get_balance: checks your stop balance without spending anything.
With a free test key: 10 stops per call, GPS coordinates only, no stops spent.
With a live key: 1 stop per stop sent, same as the API.

Add Otiggo to Claude Code

claude mcp add --transport http otiggo https://app.otiggo.com/mcp \
  --header "Authorization: Bearer otg_test_..."

Hosted server, nothing to install: https://app.otiggo.com/mcp. Keys and documentation: Route optimization API documentation

CONSTRAINTS

Real-world constraints, handled

The same rules as the ones used in the Otiggo app.

Per-stop deadlines

Set a deadline on a stop: the response flags the stops that would be late.

Service time

A service duration specific to each stop, from 0 to 60 minutes.

Start, return and tolls

Start point, optional return point, departure time and toll avoidance.

Balance at hand

Your stop balance is returned with every call and available on a dedicated route.

Route optimization API frequently asked questions

How is the route optimization API billed?: Per stop, prepaid: you buy a pack (2,000, 10,000, 50,000 or 250,000 stops) and every stop sent in a call uses 1 stop from your balance. There is no subscription or commitment, and stops never expire.
What happens if a call fails?: A call that fails (an address that cannot be geocoded, an engine error) is not charged: your stop balance is restored.
Do I need an Otiggo account to use the API?: No. You can buy a pack with just an email address: the API key is emailed to you after payment. Otiggo customers manage their keys and balance from Settings → API in the web app.
How many stops can I send per call?: Between 2 and 200 stops per call. Each stop is described by GPS coordinates or by a full address (street, postal code, city), with an optional deadline and service time.
Which constraints does the API handle?: The start point, an optional return point, the departure time, per-stop deadlines (late stops are flagged in the response), per-stop service time and toll avoidance. The response contains the optimized order, distance, duration and estimated arrival times.
Can I use the API from an AI assistant (MCP)?: Yes. Otiggo hosts an MCP server at https://app.otiggo.com/mcp: Claude Code, Cursor or any compatible MCP client can call optimize_route and get_balance with your API key. A free test key (10 stops per call, GPS coordinates) lets you try it without spending stops; a live key spends 1 stop per stop sent, like the API.
Where is the documentation?: The documentation (request format, response, error codes and a curl example) is at www.otiggo.com/developers/en, alongside pack purchase.

Explore also

Ready to optimize routes from your own software?

Pick a pack, get your key by email and make your first call.