Best route optimization APIs for field service
- September 17, 2026
- 9 mins
Scheduling field technician jobs is a fundamentally different problem from parcel delivery. Complexity does not come from stop density but from the richness of the assignment constraints: the right technician, with the right skill, at the right time, in their own territory. Modeled poorly, that reality produces schedules that are theoretically optimal and impossible to run.
This article compares eleven route optimization APIs (Kardinal, Solvice, LogisticsOS, NextBillion AI, Google, HERE, Timefold, GraphHopper, Verso, Routific, Mapbox) on their ability to handle the specific constraints of field service operations: maintenance, after-sales, telecom, energy, inspections, home healthcare.
Key takeaways
What makes field services genuinely complex
Assignment is the heart of the problem
In parcel delivery, any driver can in theory make any delivery. In field service, that is almost never true. Every job requires specific technical skills, and a technician sent to a job they are not qualified for means a wasted trip at best and a liability issue at worst. The skill constraint is not a functional detail: it is the central constraint the whole schedule is built around.
The customer appointment is a contractual constraint
Unlike delivery, where the time slot is often indicative, the customer appointment in field service is contractual. A technician who misses the agreed window causes immediate dissatisfaction and sometimes contractual penalties.
Job duration varies
In delivery, service time at each stop is stable. In field service, a job can run from 30 minutes to several hours, and that duration often depends on the fault found on site or on the technician sent. Poor duration estimates throw the whole day's schedule off balance.
Territory and continuity preferences
Field service operators generally organize technicians by territory, a strong preference the optimizer should respect by default without turning it into a hard rule. On long-term maintenance contracts, sending the same technician to the same customer cuts ramp-up time and leverages the knowledge built up on that equipment.
Emergencies and re-optimization
Field service faces structural disruptions: urgent breakdowns to slot in, cancelled jobs, technicians held up longer than planned. The ability to re-optimize schedules during the day without rebuilding everything is a key productivity factor.
The critical constraints for a field service API
Three levels of requirement shape the market: the classic base that everyone covers, the intermediate constraints that separate the good from the average, and the advanced constraints that genuinely make the difference in the field.
Working time and technician count
The fundamental objectives of any job scheduling.
Covered by: All vendors except Mapbox.
Appointment windows
Covered everywhere, with widely varying levels of precision.
Covered by: All vendors.
Emergency prioritization
Ranking jobs as urgent, scheduled or discretionary.
Covered by: All vendors except Mapbox.
Spare part pickup
Collecting a part at a depot before heading to the customer.
Covered by: All vendors.
Minimize appointment lateness
Explicitly penalizing arrivals outside the contractual window.
Covered by: Kardinal, Solvice, LogisticsOS, Routific, Timefold, NextBillion AI and Google. Absent at GraphHopper, Mapbox and Verso.
Service time by technician
Adjusting job duration to the seniority of the technician assigned.
Covered by: Kardinal, Solvice, Google, HERE, Verso and LogisticsOS. Absent at Routific, Timefold, NextBillion AI and GraphHopper.
Workload balancing
Spreading working time fairly across the day.
Covered by: Kardinal, Routific, NextBillion AI, Solvice, GraphHopper and LogisticsOS. Absent at Timefold, Google, HERE, Mapbox and Verso.
Predictive traffic
Expected traffic is factored in before optimization, not corrected afterwards.
Covered by: Kardinal, NextBillion AI, Solvice, GraphHopper, Google, HERE and Mapbox. Absent at Routific, Timefold and Verso.
Break allowed during service
Interrupting an ongoing job for a mandatory break, then resuming it.
Covered by: Kardinal only, out of the eleven solutions tested.
Real-time re-optimization
Recalculating schedules when a technician runs late or an emergency comes in.
Covered by: Kardinal, Timefold, NextBillion AI and Solvice.
Lexicographic optimization
Meeting every contractual appointment first, then minimizing travel.
Covered by: Kardinal and HERE only.
Preferred technician or continuity
Favoring a senior on complex cases, or the one who usually handles the customer.
Covered by: Kardinal, Timefold, Solvice, GraphHopper, HERE and LogisticsOS. Partial at Google.
Route compactness
Keeping each technician route geographically tight.
Covered by: Kardinal, Solvice and LogisticsOS only.
Maximum distance from home base
Capping how far a technician can travel from their home or depot.
Covered by: Kardinal only in full. Partial at NextBillion AI, Solvice and LogisticsOS.
Two-technician synchronization
For two-person jobs (electrician and crane operator, doctor and nurse).
Covered by: Solvice only, ahead of Kardinal included.
Field service API comparison
Kardinal
97% coverage · 1st/11Kardinal is the most complete solution for field service operations, with a particularly wide gap on advanced assignment constraints. It is the only vendor to combine real-time re-optimization, lexicographic optimization, maximum distance from home base and breaks allowed during service, the last of which no other vendor in the panel covers.
Its only real gap in this sector: synchronizing two technicians on the same appointment, available only from Solvice.
Solvice
78% coverage · 2nd/11Solvice shares second place with LogisticsOS. It covers route compactness alongside Kardinal, service time that depends on the technician, and the customer-technician continuity preference.
Its exclusive is absolute: it is the only solution in the panel, Kardinal included, to handle synchronizing two technicians on the same appointment.
LogisticsOS
78% coverage · 2nd/11LogisticsOS finishes level with Solvice and covers the same advanced fundamentals: route compactness, service time by technician, continuity preference.
It stands out on cost modeling, notably guaranteed minimum revenue per assigned technician, level with Google, which matters to operators mixing employees and contractors.
NextBillion AI
72% coverage · 4th/11NextBillion AI covers the fundamentals well: predictive traffic, real-time re-optimization, workload balancing across technicians. What it lacks is the finest field service layer: no technician-customer continuity preference, no service time by technician, no route compactness.
Google covers CO₂ reporting per technician and guaranteed minimum revenue, but does not cover real-time re-optimization within this constraint scope, nor the technician-customer continuity preference beyond partial coverage.
HERE
71% coverage · 5th/11HERE is the only solution besides Kardinal to offer lexicographic optimization, and it covers the continuity preference as well as service time by technician. Its weakness: real-time re-optimization is not covered.
Timefold
54% coverage · 7th/11Timefold fully covers real-time re-optimization and the technician continuity preference, two points where it joins Kardinal, but offers no predictive traffic and lags on the fundamentals.
GraphHopper
54% coverage · 7th/11GraphHopper covers the continuity preference and workload balancing, but neither real-time re-optimization nor lexicographic optimization.
Verso, Routific and Mapbox
46% · 43% · 29%These three solutions are not built for the complexity of field service.
- Verso (46%) stays limited to basic operations, without complete real-time re-optimization or continuity preference.
- Routific (43%) covers some fundamentals (workload balancing, emergency prioritization) but lacks the advanced assignment capabilities.
- Mapbox (29%) is not positioned for operational technician scheduling.
