Skip to main content

Container event (webhook)

You can specify a webhook in Settings > Integrations to listen in on containter events. Chaine will send new container events as we receive them from the different SeaLines. If there is a new event or change in an existing event (i.e. for ETA events, a change in date-time), we will push those events to your webhook. If there is no change, we won't emit duplicate events. See here for a complete list of events

Although the container events can be mapped to any format in the Integrations settings when creating an integration, the default format is:

Content type: application/json

Request body schema:

PropertyTypeDescription
shipment_idstringYour unique shipment id provided in the tracking registration
unique_container_idstringYour unique container id provided in the tracking registration
chaine_reference_idstringChaine's unique container id provided in the tracking registration
container_numberstringSeaLine issued container number
bill_of_lading_numberstringSeaLine issued bill of lading number
event_modestringThe mode of the container event. Values are "land" or "sea"
event_typestringThe type of event of values 'Inland origin', 'Origin port', 'Destination port', or 'Inland destination'.
event_codestringChaine event code for the event. See list of event codes
event_descriptionstringChaine normalized event description for the event code. See list of event descriptions
raw_event_descriptionstringThe raw event description from SeaRates which is the raw event description from the sealines
datestringThe date-time of the event. This could be an estimated or actual value depending on the event.
is_etabooleanSpecifies if the date is an estimated date-time or actual.
locationLocationLocation of the event.
vesselVesselVessel information if it is available for the event. Not provided for land events.
voyagestringVoyage number if it is available for the event. Not provided for land events.

Location The location object.

PropertyTypeDescription
namestringYour unique shipment id provided in the tracking registration
citystringYour unique container id provided in the tracking registration
statestringChaine's unique container id provided in the tracking registration
countrystringSeaLine issued container number
countryCodestringSeaLine issued bill of lading number
unlocodestringThe mode of the container event. Values are "land" or "sea"
latitudenumberThe type of event of values 'Inland origin', 'Origin port', 'Destination port', or 'Inland destination'.
longitudenumberChaine event code for the event. See docs.

Vessel The vessel object

PropertyTypeDescription
namestringYour unique shipment id provided in the tracking registration
imostringYour unique container id provided in the tracking registration
call_signstringChaine's unique container id provided in the tracking registration
mmsistringSeaLine issued container number
flagstringSeaLine issued bill of lading number

Example event

{
"shipment_id": "a456-426614174000",
"unique_container_id": "a917-418374931111",
"chaine_reference_id": "123u0987-e89b-12d3-a456-426614174000",
"container_number": "EGHU1111111",
"bill_of_lading_number": "MEDUPD111111",
"event_mode": "sea",
"event_type": "Destination port",
"event_code": "CDD",
"event_description": "Container discharge at destination port",
"raw_event_description": "Container discharged at New York City ",
"date": "2022-04-30 13:00:00",
"is_eta": false,
"location": {
"name": "New York City",
"city": "New York City",
"state": "New York",
"country": "United States",
"countryCode": "US",
"unlocode": "USNYC",
"latitude": 40.71427,
"longitude": -74.00597
},
"vessel": {
"name": "APL SENTOSA",
"imo": 9632040,
"call_sign": "9HA5180",
"mmsi": 215560000,
"flag": "MT"
},
"voyage": "0TUNLS1MA"
}