Update a Detention and Demurrage Optimization Shipment

Updating shipments with Detention and Demurrage Optimization follows the standard ocean shipment update process based on your original shipment type:

• For Port to Port Shipments: Follow Ocean Port to Port shipment updates
• For RoRo Shipments: Follow RoRo shipment updates
• For Extended Ocean: Follow Extended Ocean update workflows

You can add identifiers, modify attributes, or add events using the same API endpoints and workflows for your shipment type.

Update Methods

Detention and Demurrage Optimization supports all the same update methods as standard ocean tracking:

1. Add Information to an Existing Shipment

Add Identifiers - Append new identifiers like BOOKING_NUMBER, CONTAINER_ID, etc., to an existing shipment through a POST request.

Update Shipment Attributes - Modify custom attributes associated with your shipment.

2. Replace an Existing Shipment

Full Shipment Replacement - Completely replace shipment data through a PUT request after retrieving the current shipment object.

API Endpoints

All updates use the same API endpoints as standard ocean shipments:

• POST /api/v4/shipments/tracking - Add information to existing shipment
• PUT /api/v4/shipments/tracking - Replace existing shipment
• GET /api/v4/shipments/tracking/{id} - Retrieve current shipment data

Example: Adding Container ID to Detention and Demurrage Shipment

{
  "id": "2b1911da-d58c-4f1a-8c6b-55dc1e06df39",
  "identifiers": [
    {
      "type": "BILL_OF_LADING",
      "value": "213953651"
    },
    {
      "type": "CARRIER_SCAC",
      "value": "MSCU"
    },
    {
      "type": "CONTAINER_ID",
      "value": "MEDU1234567"
    }
  ]
}

The response will include the updated identifiers, and if the container reaches a terminal with project44 data connectivity, enhanced Detention and Demurrage tracking will automatically be applied.

Error Handling

Error handling follows the same pattern as standard ocean shipments:

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

See Error Response Codes for more information.