Skip to main content
Terminal49 sends webhook notifications for over 30 events across the container lifecycle. Each event represents a specific change to a tracking request, shipment, or container. Subscribe to individual events when creating a webhook, or subscribe to all events and filter in your handler.

Tracking request events

These events fire when a tracking request changes status.
EventDescription
tracking_request.succeededShipment created and linked to the tracking request. Your tracking is active.
tracking_request.failedThe tracking request failed. The carrier could not find the shipment.
tracking_request.awaiting_manifestThe carrier has not yet manifested this shipment. Terminal49 will retry automatically.
tracking_request.tracking_stoppedTerminal49 is no longer updating this tracking request (shipment delivered or manually stopped).

Transport milestone events

These events map to physical milestones in a container’s journey. They fire in roughly chronological order as a container moves from origin to destination.

Origin

EventDescription
container.transport.empty_outEmpty container picked up at port of lading.
container.transport.full_inFull container returned to port of lading.
container.transport.vessel_loadedContainer loaded onto the vessel at port of lading.
container.transport.vessel_departedVessel departed the port of lading.

Transshipment

EventDescription
container.transport.transshipment_arrivedContainer arrived at a transshipment port.
container.transport.transshipment_dischargedContainer discharged at the transshipment port.
container.transport.transshipment_loadedContainer loaded onto a new vessel at the transshipment port.
container.transport.transshipment_departedVessel departed the transshipment port.

Feeder vessel

EventDescription
container.transport.feeder_arrivedContainer arrived on a feeder vessel or barge.
container.transport.feeder_dischargedContainer discharged from the feeder vessel or barge.
container.transport.feeder_loadedContainer loaded onto a feeder vessel or barge.
container.transport.feeder_departedFeeder vessel or barge departed.

Destination

EventDescription
container.transport.vessel_arrivedVessel arrived at the port of discharge.
container.transport.vessel_berthedVessel berthed at the port of discharge.
container.transport.vessel_dischargedContainer discharged from the vessel at the port of discharge.
container.transport.availableContainer is available for pickup at the destination.
container.transport.full_outContainer picked up (gated out) at the port of discharge.
container.transport.empty_inEmpty container returned at the destination.

Rail (inland moves)

EventDescription
container.transport.rail_loadedContainer loaded onto a rail car.
container.transport.rail_departedRail car departed.
container.transport.rail_arrivedRail car arrived at the inland destination.
container.transport.rail_unloadedContainer unloaded from the rail car.
container.transport.arrived_at_inland_destinationContainer arrived at the final inland destination.

ETA and estimate events

These events fire when an estimated arrival time changes.
EventDescription
shipment.estimated.arrivalETA changed for the port of discharge.
container.transport.estimated.arrived_at_inland_destinationETA changed for the inland destination.

Container update events

These events fire when container attributes change.
EventDescription
container.createdA new container was added to a shipment. Common for bookings where containers are assigned after sailing.
container.updatedOne or more container attributes changed (weight, seal number, equipment type, etc.). The payload includes the updated fields.
container.pod_terminal_changedThe port of discharge terminal assignment changed for the container.
container.pickup_lfd.changedThe terminal Last Free Day (LFD) changed.
container.pickup_lfd_line.changedThe shipping line Last Free Day (LFD) changed.

Payload structure

Every webhook notification follows the same structure: a data object containing the event metadata, and an included array with the related shipment, container, and event objects. See Payload Examples for complete JSON payloads for each event type.