Event / Milestone - JSON Specification

Summary

Use this format to send or receive events (milestones) related to a shipment.

NameDescription
RootThe top level document
EventA single event or milestone related to a shipment.
LocodeA UN/LOCODE
AddressA physical location.
ReceivedByPartyThe person on file having signed for receipt of goods.
AttachmentA file attachment
NameData TypeDescriptionRequired
doc_typeStringAlways event_json
eventsArray<Event>Array of events
versionStringThe version of the specification being used.
NameData TypeDescriptionRequired
actual_dateDateTime

The date the event actually occurred. (Must be in the past)'

Always include actual_date or estimated_date. You may include both.

agent_referenceStringReference number provided by the agent
booking_referenceStringThe reference number assigned to the booking by the booking party
carrier_booking_numberStringThe booking number provided by the carrier
carrier_scacStringCarrier's Standard Carrier Alpha Code (SCAC)
container_numberStringContainer number
container_type_codeStringISO 6346 container type code (like 20GP)
estimated_dateDateTime

The date the event is estimated to occur. (May be in the past or future)

Always include actual_date or estimated_date. You may include both.

event_codeStringCode representing the type of eventYES
event_code_contextStringAdditional context information about the event.
event_descriptionString

A description of the event.

Some systems may have different descriptions for the same event across shipments. For example, a security filing event may include the filing number in the description. Therefore, you should always code against the event_code, not the description.

event_locationAddressDeprecated - Please use location instead. event_location will be removed in a future release.

The location associated with the event. Only city, state, and country will be processed
event_messageStringAny notes for the event
event_reason_codeStringA code representing the reason for the event. Typically different than the event code
event_unlocodeLocodeThe UN/Locode where the event took place (or will take place).
forwarder_controlling_branch_codeStringThe forwarder's main branch responsible for the shipment
forwarder_referenceStringShipment reference number assigned by the freight forwarder
gross_weight_kgsDecimalThe gross weight in kilograms for the shipment
house_billStringHouse bill of lading number
imo_numberStringInternational Maritime Organization (IMO) number.
import_entry_numberStringImport entry number associated with the shipment
locationAddressThe location associated with the event.
maritime_mobile_service_identityStringA Maritime Mobile Service Identity (MMSI) is a nine-digit number that uniquely identifies ship stations, ship earth stations, coast stations, coast earth stations, and group calls.
master_billStringMaster bill of lading number
parcel_referenceStringReference number used for tracking the parcel associated with the shipment
pro_numberStringPro number for a truck shipment
quantityIntegerThe number of packages in the shipment
received_byReceivedByPartyThe party on file having signed for receipt of the shipment.
receiving_exception_codeStringAn exception code for the products/lading
shipper_referenceStringReference number provided by the shipper
source_account_idStringA unique identifying code for the account that controls the shipment in a multi-tenant environment.This field is output only.
source_system_shipment_uidStringA unique identifying code from the system of record for the related shipment.YES
stop_numberDecimalThe stop number for the shipment event
transmission_uidStringA one-time unique identifying code for this transmission of the shipment in question. Used for tracing and logging purposes.
transport_modeStringMode of transportation (AIR, ROAD, SEA, RAIL)
vessel_nameStringThe name of the vessel, typically for ocean shipments.
voyage_numberStringThe voyage or flight number.
NameData TypeDescriptionRequired
descriptionStringA description of the port (like Long Beach)
unlocodeStringA valid UN/LOCODE (like USLGB)
NameData TypeDescriptionRequired
cityStringThe city.
countryStringThe 2-Digit ISO 3166 Alpha-2 Country Code. Like 'US'
country_nameStringThe full name of the country like “United States”
stateStringThe state, province, or administrative division code
NameData TypeDescriptionRequired
emailStringThe primary email address associated with the person
nameStringThe person's name
phoneStringThe primary phone number associated with the person
NameData TypeDescriptionRequired
contentBase64A Base64 encoded string of the file content
created_atDateThe timestamp this document was attached.
created_byUserThe user account / party responsible for adding the attachment.
file_nameStringThe name of the file
file_type_codeStringA short code representing the logical type of file. (You might use 'INV' for an invoice.)
file_type_descriptionStringA descriptive file type like 'Invoice to customer X'
media_typeStringThe Media Type of the file (also known as MIME Type or Content-Type)
memoStringInformation regarding the contents of the file.
privateBooleanIf true, attachment is considered a private attachment.
source_system_uidStringA unique identifying code from the system of record for this attachment.

Example