Integrations & API
Live tank and GPS data feed the theft checks and fuel plans; fuel-card files feed transactions and negotiated pricing; pricing networks feed daily station prices; your TMS feeds dispatch routes — or push routes from any TMS with the API.
Integrations
Telematics, fuel cards, pricing networks, dispatch and driver messaging plug into one fuel record. Pick yours below; the API covers everything else.
Live tank level, GPS and driver behavior
Samsara
Motive
Geotab
ISAAC
Catena TelematicsTransactions and negotiated pricing
Comdata
WEX / EFS
QuikQ
Relay PaymentsDaily station prices
Love's
Pilot Flying JWhere fuel plans and coaching land
TelegramWhat each feed powers
Live tank and GPS data feed the theft checks and fuel plans; fuel-card files feed transactions and negotiated pricing; pricing networks feed daily station prices; your TMS feeds dispatch routes.
Live tank level and GPS position, plus MPG, idle, cruise control and the rest of the driver metrics.
Where the truck was and what its tank did on every fill-up is what the theft checks verify a transaction against, and what the optimizer sizes a fuel plan from.
Powers
Sources: Samsara · Motive · Geotab · ISAAC · Catena Telematics
Transaction files and your negotiated pricing.
Every purchase lands on the right vehicle and is reconciled against the gallons it burned; the discounts are what the optimizer plans on, not the pump price.
Powers
Sources: Comdata · WEX / EFS · QuikQ · Relay Payments
Daily station prices.
Fuel plans are priced at each stop on the day they are built, and price-movement alerts reach drivers before prices change.
Powers
Sources: Love's · Pilot Flying J
Dispatch routes, so loads become routes on their own.
Alvys and DataTruck loads are polled every five minutes, Samsara and Motive routes arrive through their telematics connections, and any other TMS pushes routes through the API. When the truck reaches the first stop, the fuel plan is built and sent to the driver.
Powers
Sources: Alvys · DataTruck · Samsara and Motive routes · any TMS via the API
Where fuel plans, price alerts and coaching notes land.
The ELD tablet message, Telegram on the driver’s phone, or SMS: whichever channel the driver already uses. One switch in Settings covers every message the account sends to a driver.
Powers
Sources: Telegram · SMS · ELD in-cab messaging
Public API
A dispatch route goes in; a fuel plan comes back, with the same stops, gallons, negotiated prices and ETAs your dispatchers see in the Fuel Optimizer. If your TMS is not on the wall above, this is how it connects.
Live keys start with nvl_live_, sandbox keys with nvl_test_. Give it only the scopes it needs: routes:write, routes:read, vehicles:read, drivers:read.
An external id, the vehicle’s unit number or VIN, the driver’s name and the stops with their times. Push the same external id again and the route is updated; active routes are never changed.
Status moves pending → draft → planned → active → completed. Once the plan exists you get its stops, gallons, prices and ETAs: the same plan the driver is sent.
# illustrative; the docs are the contract
curl https://app.novilfleet.com/v1/routes \ -H "Authorization: Bearer nvl_live_…" \ -H "Content-Type: application/json" \ -d '{"externalId":"load-24016", "vehicle":{"unitNumber":"216"}, "driver":{"name":"Alfredo Martinez"}, "stops":[{"address":"Logan, OH","plannedAt":"2026-09-09T06:00:00-05:00"}, {"address":"San Benito, TX","plannedAt":"2026-09-14T09:00:00-05:00"}]}'
| Method | Path | What it does |
|---|---|---|
| GET | /v1/me | Who am I: the key, its scopes and tenant |
| POST | /v1/routes | Push a dispatch route: external id, vehicle unit or VIN, driver name, stops with times |
| GET | /v1/routes/{id} | Status (pending → draft → planned → active → completed) and the fuel plan with stops, gallons, prices, ETAs |
| GET | /v1/routes | List routes |
| DELETE | /v1/routes/{id} | Withdraw a route that has not gone active |
| GET | /v1/vehicles | Vehicles, for matching unit numbers and VINs |
| GET | /v1/drivers | Drivers, for matching names |
Keys are created under Settings › API Keys and carry the scopes routes:write, routes:read, vehicles:read, drivers:read. Base URL https://app.novilfleet.com/v1.
Developer docs
Quickstart, authentication, errors, rate limits, versioning, guides and the full reference live at app.novilfleet.com/docs. Start with these three.
From a new key to a fuel plan in six requests.
Open in the docs Getting startedBearer API keys, the four scopes they carry, and the difference between live and sandbox keys.
Open in the docs APIEvery endpoint, field and status, rendered from the OpenAPI contract at /v1/openapi.json.
Open in the docsAlso in the docs
Next step
Walk through your fleet data and identify where cost, loss, and efficiency can improve. Use our Calendly scheduler to pick a time that works for you.
