# RouteDesk Lead Intake API

> Documentation for the RouteDesk lead intake API: how lead vendors deliver leads straight into an auto transport broker's RouteDesk account.

One endpoint, `POST /api/v1/public/leads`, authenticated with a broker-issued Auth Key. For a coding agent, the full reference below has everything needed to build an integration.

## Docs

- [Full reference for agents](https://developer.routedesk.com/llms-full.txt): the whole documentation in one Markdown file
- [OpenAPI 3.1 spec](https://developer.routedesk.com/openapi.json): request schemas for both formats, auth, and every response

## Pages

- [Overview](https://developer.routedesk.com): What the lead intake API does and how to send a first lead.
- [Build with an AI agent](https://developer.routedesk.com/ai-agents): Hand these docs to Claude, Codex or another coding agent and have it build the integration.
- [Authentication](https://developer.routedesk.com/authentication): How the Auth Key works and how to keep it safe.
- [Create a lead](https://developer.routedesk.com/create-a-lead): Every field the endpoint accepts, with accepted values.
- [Responses and errors](https://developer.routedesk.com/errors): Each status code the endpoint returns and what to do about it.
- [Rate limits and retries](https://developer.routedesk.com/rate-limits): How many requests you can send and how to retry safely.
- [Testing your integration](https://developer.routedesk.com/testing): How to prove an integration works before sending real leads.
- [Already on BATS?](https://developer.routedesk.com/legacy-format): Keep the payload you already send. Change the URL and the key.
- [Changelog](https://developer.routedesk.com/changelog): Dated changes to the API and to these docs.