For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SupportDashboard
GuidesAPI Reference
GuidesAPI Reference
  • Getting Started
    • Introduction
    • Authentication
    • Quickstart
  • Core Concepts
    • Prefixed IDs
    • Pagination
    • Error Handling
    • Rate Limits
LogoLogo
SupportDashboard
On this page
  • Welcome to the Envoy AI API
  • Base URL
  • Core resources
  • Authentication
  • How it works
  • Next steps
Getting Started

Introduction

AI-powered freight logistics automation through a single REST API.

Was this page helpful?

Authentication

Every API request requires authentication via Bearer token or API key.
Next
Built with

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

EnvironmentURL
Productionhttps://tryenvoy.ai/api/v1
Staginghttps://staging.tryenvoy.ai/api/v1

Core resources

The API is organized around six core resources:

ResourceDescription
LoadsFreight shipments with origin, destination, equipment type, and rate details.
CarriersMotor carriers identified by MC and DOT numbers. Verified for safety and fraud.
OutreachesRecords of automated carrier outreach (calls, emails) tied to specific loads.
OffersRate offers on loads. Track status through pending, accepted, or rejected.
API KeysProgrammatic credentials scoped to your organization.
OrganizationsOrganization-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 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

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

Quickstart

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

API Reference

Full reference for every endpoint, schema, and parameter.