URL format
The deep link URL pattern is:{identifier} with the container number, BOL, booking number, or reference number you want to look up.
| Identifier type | Example | URL |
|---|---|---|
| Container number | TCLU6718159 | https://app.terminal49.com/shipments/find?q=TCLU6718159 |
| Bill of lading number | MEDUFR030802 | https://app.terminal49.com/shipments/find?q=MEDUFR030802 |
| Booking number | BKG12345678 | https://app.terminal49.com/shipments/find?q=BKG12345678 |
| Reference number | PO-2024-00123 | https://app.terminal49.com/shipments/find?q=PO-2024-00123 |
How resolution works
The deep link searches your Terminal49 account and redirects to the best match, in this order:- Exact container number match → Opens the shipment detail page with that container selected
- Exact shipment number or reference number match → Opens that shipment’s detail page
- First container result (partial match) → Opens the associated shipment with that container selected
- First shipment result (partial match) → Opens that shipment
- No match found → Falls back to the shipments list with the search query pre-filled, so the user can refine manually
The deep link only matches shipments and containers tracked in your Terminal49 account. If an identifier isn’t found, check that the shipment is actively tracked and that the reference number has been added.
Use cases
Link from a TMS or ERP
If your TMS or ERP stores container numbers or purchase order numbers, you can build a deep link for each record. This gives your logistics team one-click access to real-time tracking data without leaving their primary workflow. For example, if your system stores a container number per shipment record, construct the URL as:Link from a spreadsheet
Add a formula column to your shipment spreadsheet that generates a clickable Terminal49 link. Works in Google Sheets, Excel, and most spreadsheet tools.A2 contains the container number, BOL, or reference number.
Link from Slack or email notifications
Include deep links in automated alerts so recipients can jump directly to the relevant shipment:Link from webhook handlers
When processing Terminal49 webhook events, you already have the container number or BOL in the payload. Construct a deep link to include in your internal tools, ticketing systems, or dashboards:Link from internal dashboards or BI tools
Embed deep links in Looker, Metabase, Retool, or similar tools. For example, in a SQL-based dashboard, construct the link in your query:Customer portal integration
If you build a customer-facing portal, deep link your customers directly to their shipment status in Terminal49 using the PO number or reference they already know. No need to store or expose Terminal49 internal IDs.Supported identifiers
The deep link matches against these identifier types:- Container number — the standard ISO container number (e.g.,
TCLU6718159). Matched against tracked containers in your account. - Master bill of lading — the original BOL number used to create the tracking request.
- Booking number — the carrier booking reference.
- Reference numbers — any custom reference numbers you’ve added to the shipment or container (e.g., purchase order numbers, house bill of lading numbers, internal IDs).
Adding reference numbers
To deep link using your internal identifiers, attach reference numbers to shipments or containers in Terminal49. There are three ways to do this.When creating a tracking request
Includeref_numbers in the tracking request payload:
By editing a shipment
By editing a container
Related guides
Tracking Widget
Embed tracking on your website
Webhooks
Get notified when shipments update
Tracking Request Lifecycle
Understand request statuses