OptimoRoute API
A documented public REST API (v1.36) ships on every paid tier with in-app key generation, covering orders, routes, planning, drivers, and completion details. Auth is a single API key in the query string. No webhooks; polling and a 5-concurrent-request cap shape integrations.
Frequently asked questions
OptimoRoute scores C on the API Report Card. A documented public REST API (v1.36) ships on every paid tier with in-app key generation, covering orders, routes, planning, drivers, and completion details. Auth is a single API key in the query string. No webhooks; polling and a 5-concurrent-request cap shape integrations.
OptimoRoute has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
OptimoRoute is a cloud-based route planning and field service scheduling platform founded in 2012 by Marin Saric (CEO), Goran Kukolj and Frane Saric (CTO), with headquarters in Palo Alto, California and engineering in Zagreb, Croatia.
Vertical: Field Service Management, specifically last-mile delivery route optimization and field-service scheduling. Dispatchers and operations managers import orders (via CSV, the web UI, or the API), define drivers, vehicles, depots, time windows, skills and capacities, and run a planning job to produce optimized multi-stop routes.
6/10 within route optimization / last-mile delivery SaaS.
For the delivery and field-service operators that run on it, OptimoRoute is the operational system of record for: the order book (customer, address, geocode, time window, duration, required skills, capacity, priority, custom fields), drivers and vehicles (work hours, vehicle capacity and type, skills, start/end depots, breaks), optimized routes (planned sequence, ETAs, polylines, distance/time, balancing decisions), planning runs and status, live mobile events (`on_duty`, `success`, `failed`, `rejected`), and completion details (actual arrival/departure timestamps, signatures, photos, barcode scans, custom form responses, customer feedback).
Founded 2012 in Palo Alto with a Zagreb engineering office. Modern multi-tenant cloud SaaS with native iOS/Android driver apps, in-product analytics, and a clean web dispatch UI.
Hard concurrency cap of **5 in-flight requests per account/IP** forces serial/throttled integration patterns even for large daily order batches. **No outbound webhooks**, integrators must poll `get_mobile_events` on a cursor; reviewers explicitly request real-time event delivery. Full sourced list under Sources below.
Common alternatives include Onfleet, Route4Me, Routific, WorkWave Route Manager, Verizon Connect Reveal, Samsara. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically.