Skip to main content

Documentation Index

Fetch the complete documentation index at: https://nozle.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

The Nozle Routing API consists of three endpoints designed to be used together or independently:

POST /v1/routes

Compute a driving route between two addresses. Returns route geometry, distance, and duration.

POST /v1/stations/enrich-distances

Annotate your stations with route-relative positions and detour times.

POST /v1/optimize

Compute the cost-optimal fueling plan for a route, with savings vs. naive baseline.

​
Base URL

https://api.nozlerouting.com

​
Common Conventions

All endpoints:
  • Accept and return JSON
  • Require X-API-Key authentication (see Authentication)
  • Return request_id in responses for support and debugging
  • Use structured error responses (see Errors)
  • Are subject to rate limits (see Rate Limits)

​
Pipeline Usage

The three endpoints are typically used in sequence, but partners can skip endpoints when they have the relevant data from other sources:
1

Optional: /v1/routes

Skip if you have your own routing layer and can produce a Route object directly.
2

Optional: /v1/stations/enrich-distances

Skip if your station data already includes miles_from_route_start and detour_minutes.
3

Required: /v1/optimize

The core endpoint. Always called.
See Integration Patterns for common integration architectures.