Last updated

Get Drayage Visibility Tracking Updates

Drayage Visibility tracking follows the same API endpoints and workflows as standard Ocean tracking, with additional drayage-specific milestones and route information seamlessly blended into the response.

All tracking APIs available for standard ocean shipments work with Drayage Visibility. The key difference is the additional drayage events and route stops provided when containers reach Port of Discharge or last rail terminal.

API Endpoints

Use the same four targeted endpoints as standard ocean tracking:

  1. Event History - /api/v4/shipments/{shipmentId}/eventhistory - Returns shipment events and milestones
  2. Position History - /api/v4/shipments/{shipmentId}/positionhistory - Returns shipment positions
  3. Route Information - /api/v4/shipments/{shipmentId}/tracking - Returns route segments and stop information
  4. Full Tracking History - /api/v4/shipments/{shipmentId}/tracking/history - Returns all tracking information

Enhanced Drayage Events

For shipments with drayage visibility, you'll receive additional event types specific to drayage tracking:

Event TypeDescription
ARRIVAL_AT_STOPContainer/truck arrives at any drayage location (Origin, Destination, Return)
DEPARTURE_FROM_STOPTruck departs origin with loaded container
DELIVERYContainer successfully delivered to consignee
GATE_IN_EMPTYEmpty container returned to carrier facility

For complete details on all event types and their descriptions, refer to the Ocean Shipment Schema Events.

Enhanced Route Structure

Drayage stops generated by the drayage carrier are automatically merged with the existing ocean route. The integration follows this logic in case of import drayage:

  • Origin Stop: Merges with Port of Discharge or last inland facility if location matches, otherwise added after those stops
  • Destination Stop: Added as the final delivery location in the journey
  • Return Stop: Added as the final stop for empty container return, completing the ocean journey

Error Handling

Standard ocean tracking error codes apply:

  • 400 Invalid request
  • 401 Invalid or missing credentials
  • 403 User not authorized to perform this operation
  • 404 Not Found

For complete API documentation and standard tracking workflows, refer to the Ocean tracking guide. All standard endpoints and methods work with drayage-enhanced shipments.