Manage your API keys and monitor routing activity below.
Set your account-level routing defaults. These apply to all runs that don't include a per-request override.
execution_seconds field.
Use your API key in the X-Api-Key header. Here's a minimal example:
# 1. Submit a run
# execution_seconds is optional — omit to use your account default
curl -X POST https://YOUR_API_HOST/api/v1/routing/runs \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Monday Routes",
"execution_seconds": 60,
"vehicles": [{
"id": "tech-1",
"start_location": { "lat": 33.749, "lon": -84.388 },
"start_time": "2024-06-10T08:00:00-04:00",
"end_time": "2024-06-10T17:00:00-04:00"
}],
"stops": [{
"id": "stop-1",
"location": { "lat": 33.760, "lon": -84.370 },
"duration_seconds": 3600
}]
}'
# Response: { "runId": "...", "status": "pending", "message": "Run submitted with 60s optimization time..." }
# 2. Poll for result (repeat until status = "completed")
curl -H "X-Api-Key: YOUR_API_KEY" \
https://YOUR_API_HOST/api/v1/routing/runs/{runId}
Submit real stops to the routing engine and see optimization in action — step by step
10 service stops across Atlanta, GA. The ■ navy square is the vehicle depot. Orange numbered circles are stops shown in raw submission order — unoptimized.