Last updated

Update a Shipment

Use an API endpoint to update a shipment that has already been added to project44's network.

Update a Shipment to Include Additional Identifiers

Add identifiers to a shipment that has already been created. This action uses a POST endpoint to add information to the shipment. The added information never removes or replaces previous shipment data. Users do not need to use a GET before updating a shipment's information.

During the course of tracking a shipment, project44 may discover new identifiers that relate to your shipment. These discovered identifiers are often purely informational and are not being used to determine which cargo to track – you do not need to add these to your shipment. In most cases, we strongly discourage sending these discovered identifiers when updating the shipment because this will cause project44 to track all cargo related to those identifiers. This can have unintended consequences, such as tracking more cargo than desired and changing which related shipment a container is being tracked under.

Requirements

Have the following information available:

  • Master Shipment ID (the id returned during shipment creation).
  • The new identifiers to add to the post. These can be AIR_WAYBILL, HOUSE_AIR_WAYBILL, or CARRIER_SCAC.

Workflow

Complete these steps:

  1. Prepare a POST request to /api/v4/shipments/tracking.

  2. Add the new shipment identifiers to the identifiers array.

    For example, if you want to add the CARRIER_SCAC to a shipment that was created using the HOUSE_AIR_WAYBILL, see the below schema.

JSON
{
  "id": "string",
  "identifiers": [
    {
      "type": "HOUSE_AIR_WAYBILL",
      "value": "string"
    },
    {
      "type": "CARRIER_SCAC",
      "value": "string"
    }
  ]
}

This is an example of what could be returned in the response. Null fields will not show up in the response. Please refer to the reference data for more information on required and potential null fields.

  1. Send the request.

Expected Response

You have successfully submitted the request when you receive a 200 OK response. Here is a sample of the minimum response schema:

JSON
{
  "id": "string",
  "identifiers": [
    {
      "type": "HOUSE_AIR_WAYBILL",
      "value": "string"
    },
    {
      "type": "CARRIER_SCAC",
      "value": "string"
    }
  ]
}

This is an example of what could be returned in the response. Null fields will not show up in the response. Please refer to the reference data for more information on required and potential null fields.

Errors

If there was a problem with your request, you will receive one of the following error codes:

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