Developer Reference

API Documentation

Everything you need to integrate freight data into your application. The REST API accepts JSON requests and returns JSON responses.

Get an API key Interactive API Reference Node & Python SDKs

Introduction

The FreightAPIs API provides programmatic access to carrier location data for 10 carriers (ABF Freight, Central Transport, CEVA Logistics, C.H. Robinson, Estes Express, GLS US, Saia LTL, SEKO Logistics, TForce Freight and USPS), 4,400+ global seaports, Amazon drop point locations, and the National Motor Freight Classification (NMFC) database. All endpoints share a single, consistent REST interface.

Base URL

https://freightapis.dev/api

Response Format

JSON

Authentication

Bearer token

All requests must include a valid API key. Requests without authentication will return 401 Unauthorized.

Authentication

Authenticate by passing your API key in the Authorization header as a Bearer token.

Request Header

Authorization: Bearer YOUR_API_KEY

You can generate and manage API keys from your dashboard after signing up. Each key is displayed only once at creation time - store it securely. The API also accepts the key in an X-API-Key header (used by the Postman collection and SDKs below).

curl

curl https://freightapis.dev/api/article/63321 \
  -H "Authorization: Bearer YOUR_API_KEY"

Tools & SDKs

Postman collection - import to try every endpoint; set the apiKey variable and go.
OpenAPI spec - generate a client in any language, or load it into your tooling.
Node & Python SDKs - npm install freightapis / pip install freightapis.

Rate Limits

API usage is metered monthly per account. When you exceed your plan's limit the API returns 429 Too Many Requests. Limits reset on the first day of each calendar month (UTC).

Plan	Requests / Month	Notes
Free	20	Good for prototyping
Starter	10,000	For developers building freight tools
Pro	50,000	Production workloads
Enterprise	Unlimited	SLA + priority support

Every API response includes the following rate-limit headers:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed in the current period
`X-RateLimit-Remaining`	Requests remaining in the current period

Error Codes

The API uses standard HTTP status codes. Error responses always include a JSON body with an error field containing a human-readable message.

Error response

{
  "error": "Invalid API key"
}

Status	Meaning	Description
200	OK	Request succeeded
400	Bad Request	Invalid parameters or malformed request body
401	Unauthorized	Missing or invalid API key
403	Forbidden	Your current plan does not include access to this endpoint
404	Not Found	The requested resource does not exist
429	Rate Limit Exceeded	You have exceeded your monthly request quota
500	Internal Server Error	An unexpected error occurred on our end

API Products

Choose a product to view its full endpoint reference.

Unified Locations

RECOMMENDED

6 endpoints

Look up terminals across every US carrier at once, plus coverage answers: which carriers serve a ZIP and whether a given carrier can reach it. One endpoint family.

View docs

NMFC Classification

PRO

6 endpoints

4,400+ global seaports across 210 countries by UN/LOCODE, country, shipping company, and geographic radius. Includes coordinates and carrier coverage.

View docs

Start free - no credit card

Create an API key and make your first call in minutes. 20 free calls/month on the free plan.

Get an API key → Live API status