> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.tryenvoy.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.tryenvoy.ai/_mcp/server.

# Introduction

## Welcome to the Envoy AI API

Envoy AI automates freight brokerage operations. The API gives you programmatic access to carrier outreach, load management, and offer negotiation -replacing manual phone calls and emails with intelligent automation.

With the API you can ingest loads from your TMS, automatically match them to qualified carriers, track AI-driven outreach, and manage rate offers through their full lifecycle.

## Base URL

| Environment    | URL                                  |
| -------------- | ------------------------------------ |
| **Production** | `https://tryenvoy.ai/api/v1`         |
| **Staging**    | `https://staging.tryenvoy.ai/api/v1` |

## Core resources

The API is organized around six core resources:

| Resource          | Description                                                                     |
| ----------------- | ------------------------------------------------------------------------------- |
| **Loads**         | Freight shipments with origin, destination, equipment type, and rate details.   |
| **Carriers**      | Motor carriers identified by MC and DOT numbers. Verified for safety and fraud. |
| **Outreaches**    | Records of automated carrier outreach (calls, emails) tied to specific loads.   |
| **Offers**        | Rate offers on loads. Track status through pending, accepted, or rejected.      |
| **API Keys**      | Programmatic credentials scoped to your organization.                           |
| **Organizations** | Organization-level settings and configuration.                                  |

## Authentication

The API supports two authentication methods:

* **Bearer Token** -Short-lived JWT for dashboard users and interactive sessions. Pass via `Authorization: Bearer <token>`.
* **API Key** -Long-lived credential for server-to-server integrations and TMS connections. Pass via `X-API-Key: <key>`.

See [Authentication](/pages/authentication) for details on both methods.

## How it works

1. **Ingest loads** from your TMS via the Loads API or batch endpoint.
2. **Match carriers** automatically based on lane preferences, location, and equipment type.
3. **Automate outreach** as Envoy AI contacts matched carriers on your behalf.
4. **Manage offers** through their lifecycle from creation to acceptance.

## Next steps

#### [Authentication](/pages/authentication)

Set up Bearer tokens or API keys to authenticate your requests.

#### [Quickstart](/pages/quickstart)

Create your first load and find carrier matches in under 5 minutes.

#### [API Reference](/api-reference)

Full reference for every endpoint, schema, and parameter.