Skip to main content
Release Notes

What's New

Every change, addition, and improvement to the Connect Enterprise API — published here with each release.

← Back to Docs

Connect Enterprise — Version 1.1

Customers Endpoints — retrieve your organization's customers and branches to obtain the identifiers required for quoting and booking operations.

Get Customers

Paginated endpoint to list all customers owned by your organization, including branch associations. Each customer record includes the customerNumber and customerBsn values required for booking and quoting.

View Customers docs

Customer Branches (CustomerBsn)

Each customer has one or more branches. The headquarter branch is flagged with isHeadquarter: true and is itself a valid branch for all operations. Branch identifiers are environment-specific — always retrieve them dynamically.

View CustomerBsn docs

Connect Enterprise — Version 1.0

Initial release of the Connect Enterprise API — the full OTR and Drayage quote-to-book lifecycle is now available for enterprise integrations via a single authenticated REST API.

OTR Quote & Book

Request LTL and Truckload carrier rates across the PRIMO carrier network in a single API call. The quoting endpoint supports freight class, accessorials, item dimensions, insurance, and multi-mode requests. Once you have a quote, use the booking endpoint to confirm the shipment — both endpoints follow the same request/response envelope.

View OTR docs

Drayage Quote & Book

Integrate Import and Export drayage for container movements between ports, rail ramps, and warehouses. The quote endpoint accepts market, warehouse, container type, and operation type. Booking requires the full load, terminal, shipper/consignee, and container objects — all fields are documented with endpoint-to-booking field mapping tables.

View Drayage docs

Operational Tools

Eight utility endpoints covering the full reference data surface: density calculator (with and without dimensions), OTR accessorials, package types, piece types, drayage container types, markets, HS codes, SSL codes, and terminal lookups. Each response field maps directly to a quote or booking field so you can build validation and lookup flows without hardcoding values.

View Tools docs

OAuth 2.0 Authentication

All API calls are secured with OAuth 2.0 Client Credentials. Tokens are obtained from separate DEV and PROD authorization endpoints using your client credentials. The authentication guide includes cURL examples, token response structure, and a note on scopes and authorization.

View Authentication docs