Enterprise Freight Technology

How your ERP can send freight directly to BtSh.

Enterprise logistics integration becomes much easier once one idea is clear: the BtSh Loads API is an individual-shipment contract, not a one-load-per-day limitation.

What “Send to BtSh” can look like

A logistics team may work inside SAP, Oracle, Microsoft Dynamics, a transport management system or a custom ERP. They select shipment records and click a company-defined action such as Send to BtSh. Their integration then sends one authenticated request per selected shipment.

ERP shipment rows
BtSh Loads API
BtSh load refs
Freight execution
Webhook updates

Can the Loads API send 500 loads?

Yes. If 500 shipment rows are independent loads, the ERP can issue 500 Loads API requests, concurrently within its approved rate limit. Each request gets independent validation, idempotency, pricing, a BtSh load reference and its own operational lifecycle.

Bulk Loads API is different.
It is for BtSh batch workflows such as Repeat Route and Multi-Destination. It is not required simply because an enterprise has a large number of ordinary shipments.

Why idempotency matters

Every write request uses a unique idempotency key. If the ERP times out after BtSh has already created a load, it can safely retry the same shipment using the same key instead of risking a duplicate load.

POST /api/v1/enterprise/loads
X-BTSH-Client-Id: ...
X-BTSH-Client-Secret: ...
Idempotency-Key: ERP-SHIPMENT-10482

How status gets back into SAP or Oracle

BtSh webhooks push lifecycle events to the company's registered HTTPS endpoint. Their integration can update the ERP shipment row when a load is matched, enters transit, reaches destination, is delivered or is completed.

load.created
load.matched
load.escrow_funded
load.in_transit
load.delivered
load.completed

Why exact locations matter

BtSh Connect uses geofence-grade pickup and drop-off information. Exact Google Places identity and coordinates allow Trip Master and milestone logic to reason from a real location rather than ambiguous free text.

What the enterprise keeps

The ERP can remain the enterprise system of record for internal shipment references, purchase orders, projects and planning, while BtSh executes the freight and returns operational truth: load reference, status, Trip Master events, confirmations, POD/document metadata and finance status.

Planning an enterprise freight integration?

BtSh corporate workspaces and production API access are provisioned through our enterprise onboarding team.

Explore BtSh Enterprise Shipping