Customs Broker Visibility
Project44's Customs Broker Visibility solution provides shippers with real-time visibility into customs related events for ocean shipments when the customs handling is done by a 3rd party customs broker, instead of the ocean carrier or a freight forwarder.
Data Providers
- Project44 integrates with various customs brokers to gather data on customs clearance events, documentation status, and other customs-related information.
- The data is collected through APIs, EDI, and other data exchange methods, ensuring real-time updates on the status of customs clearance for ocean shipments.
Get Tracking Updates
Get tracking information about a shipment with Customs Broker data. An ocean or extended ocean shipment must be created and added to project44's network before we can return tracking information, and the Customs Broker providers must already be integrated and configured in your project44 account. To create an ocean shipment, please follow any of the guides below:
project44 offers four targeted endpoints for returning shipment tracking information. We will focus on /api/v4/shipments/{shipmentId}/tracking/history endpoint, which returns all shipment tracking information including events, positions, and stops and route segments, which includes Customs Broker data.
Expected System Response
You have successfully submitted the request when you receive a 200 OK
response. Here is a sample of the response schema:
{ "shipment": { "id": "string", "identifiers": [ { "type": "BILL_OF_LADING", "value": "string" } ], "routeInfo": { "stops": [ { "id": "string", "type": "UNKNOWN", "location": { "id": "string", "name": "string", "identifiers": [ { "type": "PORT_UN_LOCODE", "value": "string" } ], "address": { "postalCode": "string", "addressLines": [ "string" ], "city": "string", "state": "string", "country": "US" }, "coordinates": { "latitude": 0, "longitude": 0 }, "timeZone": "string" } } ], "routeSegments": [ { "id": "string", "fromStopId": "string", "toStopId": "string", "transportationMode": "AIR", "identifiers": [ { "type": "VESSEL_NAME", "value": "string" } ] } ] }, "attributes": [ { "name": "string", "value": "string", "values": [ "string" ] } ], "relatedShipments": [ { "id": "string", "identifiers": [ { "type": "CONTAINER_ID", "value": "string" } ], "attributes": [ { "name": "string", "value": "string", "values": [ "string" ] } ], "shipmentShareLink": "string", "createdDateTime": "string", "lastModifiedDateTime": "string" } ], "shipmentShareLink": "string", "createdDateTime": "string", "lastModifiedDateTime": "string" }, "states": [ { "type": "UNKNOWN", "startDateTime": "string", "endDateTime": "string", "stopId": "string", "routeSegmentId": "string" } ], "events": [ { "dateTime": "string", "receivedDateTime": "string", "type": "UNKNOWN", "description": "string", "stopId": "string", "routeSegmentId": "string", "estimateDateTime": "string", "estimateLastCalculatedDateTime": "string", "plannedDateTime": "string", "plannedEndDateTime": "string" } ], "positions": [ { "dateTime": "string", "receivedDateTime": "string", "routeSegmentId": "string", "latitude": 0, "longitude": 0 } ] }
Expected Events
With Customs Broker Visibility, you can expect events related to customs filing, such as CUSTOMS_DOCS_FILING
, CUSTOMS_CLEARANCE
, CUSTOMS_TRANSIT_DOCS_ISSUED
and CUSTOMS_TRANSIT_DOCS_CLOSED
events. These events provide insights into the status of customs documentation and clearance processes. More information about these events can be found in the $.events section of the Ocean Shipment Schema.
Expected Identifiers
EXPORT_CUSTOMS_BROKER
and IMPORT_CUSTOMS_BROKER
identifiers are expected to be present in the shipment identifiers. These identifiers indicate the customs broker responsible for handling the export and import customs processes, respectively. More information about these identifiers can be found in the $.shipment.identifiers section of the Ocean Shipment Schema.