The API Report CardAPI Index
Routific

Routific API

Fleet / Trucking / Logistics · routific.com

Routific sells its Engine as a public REST API for route optimization, with OpenAPI specs and docs at docs.routific.com. Account creation is self-serve at dev.routific.com, but API pricing is unpublished and routes through sales. Jobs over 60 visits move to async endpoints with polling.

Last verified: July 2026Logistics & Supply Chain
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented public REST API, the Routific Engine, with OpenAPI specs and JSON payloads.
AccessGOODSelf-serve account creation at dev.routific.com with no approval gate; API pricing is unpublished and goes through sales.
CoverageGOODVRP and pickup-and-delivery optimization up to 10,000 stops; jobs over 60 visits use async endpoints with polling.
AuthGOOD
Docs & DXGOODDocs at docs.routific.com with OpenAPI specs, an llms.txt index, and prebuilt ecommerce integrations.
StabilityGOODVersions v1.6.3 through v3.0 remain available concurrently, with published OpenAPI specs for each.
Supergood: Routific shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Routific scores A on the API Report Card. Routific sells its Engine as a public REST API for route optimization, with OpenAPI specs and docs at docs.routific.com. Account creation is self-serve at dev.routific.com, but API pricing is unpublished and routes through sales. Jobs over 60 visits move to async endpoints with polling.

Tried to integrate with Routific?
SOURCES
API pricing is not published; developers must contact sales to learn cost, making evaluation difficult routific.com
Large jobs (>60 visits) must use the async /vrp-long or /pdp-long endpoints with task-polling, adding integration complexity vs synchronous /vrp docs.routific.com
Multiple concurrent API versions (v1.6.3 through v3.0) create migration uncertainty for long-lived integrations docs.routific.com
Single-account, dispatcher-centric data model in the SaaS app does not natively model partner/multi-tenant scenarios - embedders must layer their own tenancy on top of the Engine API dev.routific.com
In-day re-optimization (manual changes + updated ETAs) requires careful client-side orchestration rather than first-class real-time events academy.routific.com
ETA accuracy depends on the 179 regional ML models; coverage and quality vary by geography and the API does not expose confidence intervals or per-region quality metadata dev.routific.com
Geocoding errors send drivers to wrong addresses multiple times per week, costing 1+ hour per incident and lost customers; root cause is Google Maps geocoding rather than the Routific algorithm capterra.com
Routes are not always optimized - orders to the same location get split across different drivers on different days and multiple drivers sent to the same street/building capterra.com
Customer notifications are SMS-only or email-only per account - no mixed mode for stops that can only receive one or the other checkthat.ai
SMS notifications are an expensive add-on (~$16-19/vehicle/mo) and SMS fees vary widely by country routific.com
Only one break window allowed per driver profile, creating awkward time planning for split shifts capterra.com
Only one delivery time window per customer; no support for multi-window or cycling/non-road routes capterra.com
Drivers cannot edit or modify routes once dispatched, forcing all changes back through the dispatcher capterra.com
Dispatchers cannot track drivers from a mobile device - desktop-only live tracking UI capterra.com
CSV-only spreadsheet import; direct copy-paste from existing spreadsheets often fails formatting validation capterra.com
Customer notification messages cannot be customized per client; sender name appears inconsistently and is not always recognizable as the merchant checkthat.ai
Cost is high for non-profits and seasonal operators that only run large fleets a few times per year capterra.com