Carrier integration

Carrier integrations should use the Carriers API. It is the canonical carrier contract and combines the carrier-authorized variants of logistics requirements and ePLR.

Logistics requirements for a lane

Use the carrier lane logistics-requirements operation with the lane ID and lane authorization key supplied with the transport context. The response contains translated loading and unloading requirements, including operating hours, access restrictions, equipment, documents, cleaning, packaging, temperature, and process information where maintained.

The lane authorization key is sensitive. Do not log it or expose it in client-side applications.

ePLR check

Submit the shipper company ID, product reference number, cleaning state/procedures, and up to five previously loaded products through the carrier ePLR check. Preserve the optional tracking number for end-to-end correlation.

Query the carrier ePLR scope first when you need the configured number of previous loads and whether special cleaning is required.

The standalone Logistics Requirements API and ePLR API serve non-carrier customer scenarios. Do not mix their request shapes with the carrier endpoints.

The carrier ePLR request identifies the shipper with companyId; the lane requirements request uses the lane ID and laneAuthorizationKey. This differs from the standalone customer contracts, so use the generated Carriers API schema directly.