Build freight into your own systems.
One REST API to book shipments on your contracted lanes and follow every order on the CtrlChain freight network — from your TMS, ERP, or warehouse system.
curl https://api.ctrlchain.com/api/v1/Request/lane-booking \
-H "apiKey: $CTRLCHAIN_API_KEY" \
-d '{
"laneId": "5a1c9e7d-2b3f-4a6c-8d9e-0f1a2b3c4d5e",
"groupId": "8c2e1b4a-9d3f-4c5e-a6b7-c8d9e0f1a2b3",
"userId": "b9b0054f-000f-4e0d-a529-555f31821541",
"tailLift": false
}'
HTTP/1.1 200 OK
{
"ccaRequestReferenceNumber": "CCA2026-007873",
"ccaOrderReferenceNumber": "CCA2026-007873.1"
}Five APIs, one freight network
Everything runs over the same base URL and the same API key. Start with Users and Lanes to gather your booking ids; add Webhooks to stay in sync.
Your first call in three steps
No self-serve signup — keys are issued per company, so your integration is production-ready from day one.
Ask your CtrlChain account manager or info@ctrlchain.com. Keys are issued per enterprise and scoped to your own groups, lanes, and orders.
curl https://api.ctrlchain.com/api/v1/Lane/get-lanes \ -H "apiKey: $KEY"
Lanes are your contracted routes — every booking starts from one.
Place a lane booking — a valid request immediately creates an order — and have webhook notifications enabled so status changes are pushed to you, no polling.
See the endpoints →What teams build on it
Shippers place lane bookings straight from their planning system, on the lanes and rates already agreed with CtrlChain.
Requests guide →Pickup and delivery ETAs, confirmations, and POD approvals pushed to your systems the moment they happen.
Webhooks guide →Keep lanes, booking users, and order references aligned between CtrlChain and your own back office.
Lanes guide →