How it works
- You create a tracking request with a Bill of Lading (BOL) or container number.
- Terminal49 monitors the carrier and destination terminal for changes.
- When something changes — an ETA update, a milestone event, a container hold — Terminal49 sends a
POSTrequest to your webhook URL with the full event payload. - Your system processes the event and returns a
2xxstatus code.
Why webhooks instead of polling
| Webhooks | Polling | |
|---|---|---|
| Latency | Minutes after carrier reports | Depends on your poll interval |
| Efficiency | Only fires when data changes | Most requests return unchanged data |
| Rate limits | No API calls consumed | Each poll consumes a request |
| Complexity | Handle incoming POST requests | Build and maintain a polling loop |
| Recommended | Yes | Only for on-demand data retrieval |
What you can do with webhooks
Webhooks power most Terminal49 integrations. Common patterns include:- ETA monitoring — alert your team when a shipment’s arrival estimate changes
- LFD and availability alerts — trigger dispatch when a container clears holds and is ready for pickup
- Milestone tracking — build a complete timeline of a container’s journey from origin to destination
- Data sync — push every update into your database, ERP, or TMS as it happens
- Customer notifications — surface tracking updates to your end customers in real time
Next steps
Set up webhooks
Create your first webhook and subscribe to events.
Event catalog
Browse all available webhook events by category.