Callable routing
The same nine endpoints the clients use.
Technology · Integration · Whitepaper
Your systems already have the data.
NavTrax exposes REST endpoints for routing, resupply, layers and billing, and integrates hardware through an adapter framework. This page documents what is available, what authentication looks like, and what is not exposed.
01 / Problem statement
What this has to solve.
Integration requests fall into three groups, and they need different answers.
Push our data in. A forestry company already has cut-block boundaries and a fleet operator already has a vehicle list. Re-entering them is unacceptable.
Pull our data out. Position history, duty records, field observations and audit logs need to reach an existing system of record.
Integrate a device. A sensor, radio or airframe that is not yet supported needs a path that is not "wait for a release".
02 / Mechanism
The design, component by component.
- Authentication
- Bearer tokens scoped to a tenant and a role. Tokens are revocable, and every call is authorized against the same RBAC model the clients use — there is no privileged API bypass.
- Routing endpoints
- The nine documented routing endpoints are directly callable, including from your own systems, with the same constraint vocabulary the clients use.
- Layer registration
- Register a tile, WMS or vector source, or upload GeoJSON, KML or a shapefile export, and it becomes an organization layer distributed to devices by role.
- Resupply and commerce
- Vendor registration, catalog, cart, order and shipment endpoints, for operators who want to serve a trail or a crew.
- Billing catalog
- The plan catalog is readable, which is how the marketing site and both mobile clients render the same prices the backend charges.
- Export
- Position history, field observations, duty records and audit logs export as GPX, KML, GeoJSON and CSV. Bulk export is a documented endpoint, not a support request.
- Device adapters
- Each device class has one contract. A new receiver, radio or airframe is an adapter against that contract rather than a change to the application.
- Webhooks
- Available for order, shipment and alert state on Enterprise, so an existing system learns about a state change rather than polling for it.
- Not exposed
- We do not expose an endpoint that bypasses the emergency escalation confirmation, and we do not expose an effector interface of any kind. Both absences are deliberate.
03 / Properties
What this guarantees.
Layer ingestion
Tile, WMS, vector and file sources.
Bulk export
GPX, KML, GeoJSON, CSV.
Commerce endpoints
Vendor, catalog, cart, order, shipment.
Readable plan catalog
Which is why every surface shows one price.
Device adapter contract
New hardware without an application change.
Webhooks on Enterprise
Order, shipment and alert state.
Documented refusals
No escalation bypass, no effector interface.
04 / Reference
| Group | Purpose | Tier |
|---|---|---|
| /route/* | Nine routing and analysis endpoints | Pro |
| /layers | Register and distribute layers | Pro |
| /vendors, /products | Resupply catalog | Pro |
| /carts, /orders, /shipments | Commerce and fulfillment | Pro |
| /billing/catalog | Plan catalog, read-only | All |
| /export/* | Bulk data export | Elite |
| /audit | Audit log export | Enterprise |
| Webhooks | State change notification | Enterprise |
05 / Process
Traced, node by node.
Adapters, not integrations.
Ask us for the API documentation and the device adapter contract.