DAT Freight API

Name: DAT Freight API
Brand: DAT Freight API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceShipping Logisticsbearer9 EndpointsREST

For Agents

Look up freight rates, post and search loads, advertise truck availability, and check carrier DOT details across the DAT freight marketplace.

Install Jentic One Beta

Connect the DAT Freight API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DAT Freight API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DAT Freight API.

Look up current freight rates between origin and destination lanes

Retrieve historical rate trends for a specific freight lane

Post available loads to the DAT load board for carriers to find

GET STARTED

Start building with DAT Freight API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DAT Freight API for, with concrete tasks.

★ Broker Rate Quoting

Quote shippers in real time using current and historical lane rates from DAT instead of static rate cards. POST /rates/lookup returns a current point-in-time rate, and GET /rates/history returns trend data for the same lane. Suitable for freight brokerages building modern quoting tools or rate APIs for their shippers.

Call POST /rates/lookup for a Chicago to Atlanta dry van lane and pair it with GET /rates/history for the same lane to produce a quote with a 30-day rate trend.

Automated Load Posting and Matching

Post loads directly from a transportation management system to the DAT load board and pull matching trucks. POST /loads creates a load, GET /loads searches existing loads, and GET /trucks lists available capacity. Useful for brokers and 3PLs that already manage loads in another system.

Post a 45000 lb dry van load originating in Dallas with a delivery in Phoenix, then poll GET /trucks for matching capacity over the next two days.

Carrier Vetting Workflows

Vet carriers before tendering loads by pulling DOT-based carrier information directly from DAT. GET /carriers/{dotNumber} returns identifying details from the carrier's DOT profile. Useful for compliance teams that need a programmatic vetting step before dispatch.

Look up carrier DOT 1234567 via GET /carriers/{dotNumber} and return the operating name and authority status for the broker's vetting checklist.

Capacity Planning for Carriers

Help carriers plan repositioning by combining truck postings with rate history on candidate lanes. POST /trucks advertises availability, and GET /rates/history surfaces lanes worth deadheading toward. Suitable for fleet planners and asset-based carrier tools.

Post a truck available in Memphis on Friday, then call GET /rates/history for outbound lanes from Memphis and rank them by recent average rate.

Agent-Driven Freight Operations via Jentic

AI agents that operate inside a brokerage or carrier's TMS can call DAT through Jentic without holding the bearer token. The agent searches Jentic for the relevant intent, loads the schema, and posts loads, looks up rates, or checks carriers using credentials held in the Jentic vault. This keeps DAT credentials isolated per operator.

Use Jentic to search 'look up a freight rate', load POST /rates/lookup, and execute it with the lane and equipment type from the user's quoting request.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for dat freight api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/rates/lookup

Look up the current rate for a freight lane

GET

/rates/history

Get historical rate trends for a lane

POST

/loads

Post a load to the DAT load board

GET

/loads

Search loads on the DAT load board

POST

/trucks

Post truck availability

GET

/trucks

Search available trucks

GET

/carriers/{dotNumber}

Look up a carrier by DOT number

POST

/rates/lookup

Look up the current rate for a freight lane

GET

/rates/history

Get historical rate trends for a lane

POST

/loads

Post a load to the DAT load board

GET

/loads

Search loads on the DAT load board

POST

/trucks

Post truck availability

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DAT bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access for each call and the raw Authorization value never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'look up a freight rate') and Jentic returns the matching POST /rates/lookup operation with its input schema, so the agent calls the right endpoint without parsing the DAT integration documentation.

Time to first call

Direct DAT integration: 1-2 weeks including subscription activation, OAuth credential setup, and load posting flow testing. Through Jentic: under 1 hour to call the spec — DAT subscription still required separately.

FAQs

Specific to using DAT Freight API through Jentic.

Why is there no official OpenAPI spec for DAT Freight API?

DAT does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DAT Freight API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the DAT Freight API use?

The DAT Freight API uses bearer token authentication via the bearerAuth scheme — the access token is sent in the Authorization header. Through Jentic the bearer token sits in the vault and never enters the agent's context.

Can I post loads to the DAT load board with this API?

Yes. POST /loads adds a load to the DAT load board with origin, destination, equipment type, and weight, and GET /loads searches existing postings.

What are the rate limits for the DAT Freight API?

The OpenAPI spec does not declare explicit numeric limits. Production limits are issued under your DAT subscription — apply backoff on 429 responses and batch lane lookups where possible.

How do I look up a freight rate through Jentic?

Run pip install jentic, then search Jentic for 'look up a freight rate', load the POST /rates/lookup schema, and execute it with the origin, destination, and equipment type. Jentic injects the bearer token at call time.

Does the DAT Freight API let me look up carriers by DOT number?

Yes. GET /carriers/{dotNumber} returns DAT's carrier identity and operating data for the specified DOT number, useful for vetting workflows before tendering loads.

DAT Freight API

Connect the DAT Freight API to your agent

Capabilities

Start building with DAT Freight API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs