Event types - Traddal Developers

Every consignment timeline event is a webhook event, plus manifest lifecycle and carrier tracking.

Consignment events

Event	Fires when
`consignment.created`	A consignment is created (API, import, or dashboard)
`items.classified`	The classifier assigns HS codes to items
`duties.calculated`	A duty assessment completes
`payment.requested`	A duty payment link is issued
`payment.paid`	The payer completes payment
`email.queued` / `email.opened`	Notification emails move
`hold.placed` / `hold.released`	A hold changes state
`label.generated`	A carrier label is produced
`group.scanned`	A parcel is scanned into a processing group
`product.applied` / `product.matched`	Catalogue products attach to items
`pre_alert.created`	A pre-alert is sent
`comment`	A timeline comment is added

Document events

Event	Fires when
`document.accepted`	Staff accept an uploaded document
`document.rejected`	Staff reject an uploaded document
`document.signed`	The receiver completes an e-sign ceremony on the portal

Case events

Event	Fires when
`case.opened`	A case (dispute, claim, delivery issue, request) is opened
`case.updated`	A case changes status without closing
`case.resolved`	A case closes — resolved, rejected, won, or lost

Manifest events

Event	Fires when
`manifest.created`	A manifest is created
`manifest.linked`	A consignment links to a manifest row
`manifest.mismatch`	A linked row disagrees with declared data
`manifest.import.completed`	An uploaded manifest finishes importing
`manifest.ingest.completed` / `manifest.ingest.failed`	Automated ingest finishes or fails

Carrier events

Event	Fires when
`carrier.tracking`	Any harmonised tracking event arrives, with matched parcel IDs
`parcel_event`	Every unified parcel event (tracking, scan, or manual)
`parcel.out_for_delivery`	A parcel’s harmonised status hits out-for-delivery
`parcel.delivered`	A parcel is delivered (payload includes `signed_by` when the carrier supplies it)
`parcel.exception`	A problem status — delivery exception, failed attempt, customs hold, or return-to-sender
`parcel.estimated_delivery`	A tracking event carries a carrier-supplied estimated delivery date

The parcel.* milestone events fire in addition to the generic parcel_event and carry tracking_number, carrier, shipment_ref and external_code at the top level of data, so you can map deliveries straight onto your own order references.

Test

Event	Fires when
`test.ping`	You press the test button on the Developers page. Delivered synchronously — the response reports your endpoint’s actual HTTP status.

Use category wildcards to subscribe to a family: manifest.* receives every manifest event, including types added later.