Skip to main content

Navigo Lead Provider API

Navigo is a CRM for logistics (auto transport). These docs give external partners (Lead Providers) and system administrators a complete guide to integrating with Navigo.

Two different APIs

The platform consists of two separate APIs — each with a different audience and authentication model:

APIFor whomAuthenticationWhat it does
Public Lead APIExternal providersProvider API Key (Bearer)Submit leads and track their status
Management APISystem adminsJWT + IsAdminOnlyPositionCreate/manage providers, issue API keys

:::tip Which one do you need? If you are a partner sending leads to Navigo, you need the Public Lead API. If you are a Navigo admin managing providers, head to the Management API section. :::

Architecture overview

┌──────────────────┐ POST /public/leads/ ┌──────────────────┐
│ Lead Provider │ ───────────────────────────────► │ │
│ (external) │ GET /public/leads/{id}/ │ Navigo CRM │
└──────────────────┘ ◄─────────────────────────────── │ (backend) │
│ │
┌──────────────────┐ POST /lead_providers/create/ │ • Providers │
│ Navigo Admin │ ───────────────────────────────► │ • Leads │
│ (CRM panel) │ POST .../generate_api_key/ │ • API keys │
└──────────────────┘ ◄─────────────────────────────── └──────────────────┘

A typical integration flow:

  1. An admin creates a new provider via the Management API and generates an API key for it.
  2. The key is delivered to the provider over a secure channel (the system cannot show it again).
  3. The provider submits leads through the Public Lead API and tracks their status.
  4. Inside Navigo, the lead moves through the LEAD → QUOTE → ORDER stages.

Base URL

All endpoints live under the /api/v1 prefix. The full URL for external providers:

https://<navigo-domain>/api/v1/...

:::warning Domain Throughout these docs, https://api.navigo.example is used everywhere as a placeholder. Get the real domain from the Navigo backend team. :::

Next steps