Skip to main content
This page contains updates to Terminal49 API and DataSync only (not general product updates).
June 8, 2026
APIDashboard
Pickup & Delivery dashboard, bulk party assignment, event-driven calculated LFD, refreshed ONE/CMA CGM/Evergreen tariffs, and a wave of carrier and dashboard bug fixes

Pickup & Delivery Dashboard

A new Pickup & Delivery workspace is available in the Terminal49 dashboard, organizing containers by their pickup-and-delivery phase. View phase-grouped tables, edit pickup and delivery event datetimes inline, and sort by delivery appointment to focus on what needs to move next.

Bulk party (role) assignment

Shipment and container party roles can now be assigned and updated in bulk from the dashboard, including via CSV upload alongside other shipment and container fields. Bulk-assign consignee, shipper, notify party, and other roles across many records in a single import.

Event-driven calculated demurrage LFD

The Smart LFD calculation engine now runs event-by-event rather than on a periodic backfill. When a tariff input changes — a new arrival event, a hold release, or a tariff update — the calculated Last Free Day refreshes immediately and emits a transport event with t49_calculation as its source.

Container API reference

View the container resource

Refreshed ONE, CMA CGM, and Evergreen tariffs

Re-synthesized the demurrage tariff rule datasets for ONE (ONEY), CMA CGM (CMDU), and Evergreen (EGLV) with new effective-date periods and pipeline improvements. Calculated LFD values for these carriers now reflect their latest published tariffs.

Updates

  • t49_calculation source on the shipment timeline — events created by the Smart LFD calculation engine now surface a t49_calculation source tag in the dashboard event timeline, so you can tell at a glance which LFD updates came from a tariff calculation
  • Manual milestone edits flow through the event pipeline — user-submitted empty-in, full-out, and delivery-appointment events are now created as proper transport events. They update container attributes, fire container.transport_event webhooks, and appear consistently in the timeline like carrier-sourced events
  • Updated Wayfair arrival notice extraction — published a new versioned extraction schema for Wayfair arrival notices with refreshed gold datasets and classifier prompts, improving field-level accuracy on Wayfair documents
  • Sort container dashboard by shipment number — added Shipment Number as a sortable column on the container dashboard
  • Sort container dashboard by delivery appointment — added delivery appointment as a sortable field on the containers API and dashboard
  • PAYG billing clarification — the billing settings page now clearly explains how active free containers are counted on Pay-As-You-Go plans
  • Bookings removed from the left nav — the Bookings preview entry has been removed from the dashboard navigation while the workspace continues to evolve

Bug fixes

  • Tracking slot limit no longer blocks paying customers — Fixed an issue where the active tracking slot limit could incorrectly block paying accounts from creating additional tracking requests. The limit and its warning now apply only to free plans
  • CMDU ambiguous port events — Rejected ambiguous CMDU port events that could otherwise be attributed to the wrong leg, and excluded pre-POD events from the destination-port heuristic so inland destinations are inferred more accurately
  • YMLU POD selection — Fixed port-of-discharge selection for YMLU shipments where only container-level data was available, so the correct POD is chosen
  • NSRR top-level ETA — Fixed parsing of Norfolk Southern’s top-level ETA so rail ETAs populate when the carrier returns them at the response root
  • WMC unavailable terminal status — Where’s My Container responses that report a container as unavailable are now handled cleanly instead of failing the terminal scrape
  • Removed sort custom field columns are forgotten — Deleting a custom field used as the active sort no longer leaves the dashboard stuck on an unknown sort column
  • Map route Pylon widget — Fixed the Pylon help bubble showing on the global vessel map; it now hides and re-shows correctly when navigating in and out of the map
June 1, 2026
APIDashboard
Global vessel map general availability, Wayfair document extraction, contract product additions, and a wave of carrier and dashboard bug fixes

Global vessel map is now generally available

The global vessel map is now enabled for all accounts in the Terminal49 dashboard. Live vessel positions, voyage details, and the shipments on board are available without a feature flag, with realtime updates and analytics tracking built in.

Wayfair document extraction improvements

Released new versioned extraction schemas for three Wayfair document types — arrival notice, carrier delivery order, and cargo control document. Highlights:
  • Arrival notice now captures place of delivery (name, address, phone, available date, last free day, FIRMS code, and sublocation)
  • FIRMS code routing distinguishes rail-ramp destinations from the port of discharge, with both fields populated when both codes appear
  • Hapag-Lloyd Canada “Advice Note / Avis d’Expédition” documents are now correctly classified as arrival notices (previously misclassified as sea waybills)
  • Tighter I vs 1 disambiguation across carriers

Document processing guide

How document linking works

BL submissions without containers

You can now submit bill of lading shipments before container numbers are known. Tracking requests for BL submissions accept shipments with no containers, so you can initiate tracking earlier in your workflow and have containers attach as they’re released by the carrier.

New contract products

Added two new contract products available through your account team:
  • Lite — a lower-tier subscription for smaller-volume customers
  • Integration service fee — a separate line item for one-time integration work
Contact your account team for pricing and availability.

Updates

  • Pending tracking requests count as one slot — Pending tracking requests are now counted against a single tracking slot rather than per-container, giving free and metered plans more headroom while requests are awaiting manifest
  • HDMU mobile LFD locations — Last Free Day events from the HDMU mobile tracker now infer the correct terminal location, fixing missing per-terminal LFD displays for Hyundai (HDMU) containers
  • SSL overview no longer overwrites terminal data — Shipping line overview responses no longer overwrite terminal-sourced fields on containers, so terminal availability, holds, and fees stay authoritative when both sources are present
  • Empty-In can override terminal status — A reported empty-in event now correctly overrides a stale terminal status, so containers returned empty are reflected promptly in the dashboard and API
  • Transport event location fallbacks removed — Removed legacy fallbacks that could fill in incorrect locations on transport events. Event locations now reflect the source data directly, with no implicit substitutions

Bug fixes

  • ZIM destination ETA no longer auto-promotes to ATA — Fixed an issue where ZIM destination ETAs could be promoted to an actual arrival time prematurely, causing inland arrival dates to flip without a real event
  • Document linking via bridge shipments — Documents no longer create an intermediate link when more than one shipment is involved in a reference bridge, reducing incorrect cross-shipment links
  • Dashboard custom field date filters — Fixed an error where the not present operator failed on date and datetime custom field filters, and resolved a related stale sort issue
  • Harbor filter search — Restored search inside the dashboard’s chip-style filter dropdowns after the underlying picker upgrade
  • Trawler no_event_history with containers — Allowed the no_event_history tracker state to coexist with container records, preventing dropped updates for shipments whose carriers temporarily return no event history
May 25, 2026
APIDashboard
Tracking request custom fields API, KMTC and Termont integrations, container status in CSV export, free plan slot limits, and bug fixes

Tracking request custom fields API

You can now manage custom field values on tracking requests via the API, in addition to shipments and containers. Use the new endpoints to attach predefined custom fields when a tracking request is created — values flow through to the resulting shipment and containers once tracking starts.

List tracking request custom fields

List values on a tracking request

Create a tracking request custom field

Attach a value to a tracking request

KMTC steamship tracker

Added a direct integration for KMTC (KORP) shipments. Track KMTC containers, bills of lading, and bookings using their native SCAC, with full container, event, and route data.

New terminal integrations

  • Termont (Montreal) — added a WordPress-based scraper for Termont container availability, status, and rail-state data
  • APM Terminals — alternative scrapers — two new APM scraper integrations (apmweb_cffi and apmweb_firecrawl) are available alongside the existing APM source, so terminals can be served by whichever endpoint performs best per site

Container status in CSV export

The container dashboard CSV export now includes a Current Status column and supports filtering by current status before export, so exported files reflect exactly what you see on screen.

Report Issue from the container side panel

The container details side panel now includes a Report Issue button so you can flag a data problem directly from the container you’re viewing, without leaving the dashboard.

Multi-period tariff history for Smart LFD

The Smart LFD tariff engine now tracks multiple historical tariff periods per carrier, so Last Free Day calculations on older containers use the tariff rules that were in effect at the time. Tariff rules now also carry tariff_number and tariff_rule_number for traceability back to the source document, and synthesis_warnings surface any issues detected when a tariff was synthesized.

Container API reference

View the container resource

Updates

  • Document linking by custom fields — documents can now be linked to shipments and containers using custom field values, in addition to PO numbers, BOLs, and container numbers
  • PO number matching is more forgiving — additional common typo patterns are now matched when linking documents via PO number
  • Free plan tracking slot limits — Free accounts now meter against active tracking slots with clearer in-app usage copy, and unknown-container slot handling has been tightened
  • Inline custom field option creation — single- and multi-select custom fields now let you create new options inline from the value picker, with several follow-up polish improvements
  • Custom field filter-out option — container filters now support filtering for records where a custom field is not set
  • Quick link to shipment/container — added a button to copy a direct link to a shipment or container from the dashboard
  • EGLV Last Free Day events now include location — EGLV LFD events now carry the inland destination location so per-terminal LFD displays correctly
  • Arrival notice classification — fixed an issue where some arrival notices were misclassified as sea waybills during document processing
  • Hapag-Lloyd FIRMS code routing — clarified FIRMS code handling on arrival notice extraction so terminal routing is more reliable

Bug fixes

  • TRKU future events — TRKU events dated in the future are now classified correctly so container timelines no longer skip past upcoming events
  • HMM mobile error pages — HMM (HDMU) mobile responses that return an HTML error page are now handled cleanly instead of failing the tracker run
  • MAEU tracking — Migrated remaining MAEU traffic off the legacy tracker to MaeusynergyTracker for more reliable Maersk container data
  • Document linking edge cases — documents with both an explicit and implicit link no longer fail to link, child packets now inherit only direct links from their parent, and legacy .xls files using the roo-xls path are processed correctly again
  • Container state filters — removed the unused “loaded” and “dropped” values from the current-status filter so the dropdown only shows real states
  • Dashboard search focus — fixed an issue where selecting a recent search left the input out of focus, and tightened the global click listener that drives dropdowns
  • Disabled integrations — disabled integrations no longer appear in the credentials list
  • Unknown account handling — webhook and ingestion paths no longer raise when an unknown account is referenced
  • Sentry instrumentation — fixed a missing region on the Sentry cassette job and removed a path that could cause Sentry error reporting itself to loop
  • Knock in-app guides — improved rendering of the Knock guide banner and moved free-plan Knock syncing to commit-time so guides display reliably
May 11, 2026
APIDashboard
link.created webhook, Bookings preview, new terminal integrations, expanded CSV bulk update, and bug fixes
A new link.created webhook event fires whenever a document is linked to a shipment or container. Subscribe to it to react in real time when reference extraction connects an inbound document to your cargo — no polling required.

Event catalog

Browse all webhook events

Bookings (preview)

A new Bookings workspace is available as an early-access preview. Bookings ingests carrier schedules, surfaces gate-in cutoffs and vessel phase, and automatically initiates tracking once a booking has the schedule context it needs (POL, vessel, ETD). Contact your account team to enable the preview on your account.

New terminal integrations

  • Port Houston (Barbours Cut, S787) — added a direct API integration for container status, holds, fees, and last free day at Port Houston
  • Port of Wilmington (L194) — added a Voyager-based scraper for Port of Wilmington container data

Per-account terminal scraper selection

Accounts can now opt into specific terminal scraper integrations independently, so you can pilot new data sources or stay on the existing one on a per-account basis.

value_timestamp on shipping line LFD transport events

The value and value_timestamp fields on transport events are now always returned in the API and on webhook payloads, including for shipping line Last Free Day events. Previously these were gated by a rail data permission; you can now see when an SSL LFD was reported without extra configuration.

Container transport events

Transport events API reference

Draft demurrage tariff rules for ONE, Evergreen, and CMA CGM

Added draft demurrage tariff rule datasets for ONE (ONEY), Evergreen (EGLV), and CMA CGM (CMDU) to the Smart LFD tariff engine. Tariff rules now also carry charge_type (demurrage vs. detention) and day_count_type so calculated Last Free Day values reflect the carrier’s specific tariff structure.

Container API reference

View the container resource

Expanded CSV bulk update

The container dashboard’s CSV bulk update now supports more fields:
  • Shipment tags and reference numbers can be updated in the same CSV alongside container fields
  • Tracking request custom fields can be created and updated in bulk for tracking requests that are still pending or awaiting manifest

Manual refresh feedback

When you trigger a manual refresh on a shipment, its containers now display a refreshing state in the dashboard so you can tell which records are still updating.

Custom fields moved to Data Management

Custom fields now live under Data Management in the dashboard, and tags share the same look-and-feel as custom fields for a more consistent experience when configuring shipment metadata.

Custom Field Definitions

Custom Fields API reference

Daily email digest pacing

Daily email digests are now spaced out across the delivery window instead of being scheduled in a single burst, improving deliverability and reducing duplicate-send risk for large accounts.

Bug fixes

  • Rail LFD on container pickup — Rail Last Free Day no longer fails to update once a container has been picked up
  • APM containers on rail — Fixed an error that could occur for APM containers on rail with no equipment moves, allowing container data to load
  • HDMU LFD events — HDMU Last Free Day events now include the correct location for accurate per-terminal LFD display
  • Swire ETA fallback — Swire shipments now fall back to the tracking sheet for ETA when the primary source is missing, and route locations are extracted more reliably
  • SMLU schedule port calls — Fixed a NoMethodError affecting SMLU schedule lookups so shipments load consistently
  • POL/POD location extraction — Improved extraction of port-of-loading and port-of-discharge locations for SSPH, ZIM (ZIMU), TJFH, TXZJ/TXSJ, and YMLU shipments, reducing missing or incorrect route locations
  • Terminal scrape error handling — Failures during terminal scrape context resolution are now handled cleanly so they no longer pollute terminal-health metrics
  • Steamship tracker rate limits — Expected rate-limit errors from upstream carriers are now silenced and vessel-event extraction is instrumented for better visibility into ingestion health
May 4, 2026
APIDashboard
Global vessel map, custom field search, sensitive custom fields, expanded terminal coverage, and bug fixes

Global vessel map

The Terminal49 dashboard now includes a global vessel map showing live positions for vessels carrying your shipments. Click any vessel to see its current voyage, route, and the shipments on board. The map streams updates over a websocket connection so positions stay current without manual refresh.

Search by custom field values

Shipments and containers can now be searched by custom field values alongside built-in identifiers. Use the same search you already use for container numbers or PO numbers to find records by any custom field you’ve defined.

Custom Field Definitions

Custom Fields API reference

Sensitive custom fields

Custom field definitions now support a sensitive flag. Mark a field as sensitive to restrict its visibility to authorized users — useful for fields containing internal references, financial data, or PII.

Configurable duplicate document handling

Accounts can now configure how duplicate documents are handled at upload time. Choose whether to reject duplicates, replace the existing document, or accept both, so document intake matches your team’s workflow.

Document processing guide

How document linking works

xlsm spreadsheet support

Macro-enabled Excel files (.xlsm) are now accepted by the document upload pipeline and converted to CSV for reference extraction. Previously only .xls and .xlsx were processed; mixed Excel uploads now flow through end-to-end without manual conversion.

Destination ETA for non-US/CA containers without rail data

Containers routed to inland destinations outside the US and Canada now return a destination ETA even when no rail tracking data is available, expanding ETA coverage for international inland moves.

Container API reference

View the container resource

New terminal scrapers

  • Felixstowe — added a mobile-site-based scraper as an alternative data source, improving reliability for containers moving through Felixstowe
  • DP World Vancouver (3380) — added a public-API scraper for terminal data at DP World Vancouver

Pay-As-You-Go customers can now enter a promo code at Stripe Checkout, or follow a coupon link that pre-applies the discount during signup.

Bug fixes

  • YMLU transshipment events — Fixed spurious full-out events generated at transshipment ports and corrected port-of-discharge mismatches for YMLU shipments
  • MSC inland voyage numbers — Stabilized voyage number assignment for MSC inland feeder and barge legs so the same leg no longer appears under different voyage numbers across updates
  • ONE event timestamps — Rail unloaded and other ONE events now use port-local time consistently, fixing display and ordering issues for ONE-tracked containers
  • Bulk email CSV uploads — Fixed an issue where rows using alternative SCACs were silently dropped from CSVs submitted by email
  • Rail carrier lookup — Rail carrier resolution now considers neighboring ports, improving carrier assignment for containers transferring between adjacent rail-served facilities
  • Tideworks terminal sessions — A 403 on the CSV endpoint now clears the cached session immediately, preventing a cascade of failed terminal lookups across containers
  • Steamship tracker reliability — Proxy and firewall blocks at carrier websites are now classified as TrackerBlocked errors, surfacing a clearer failure reason and enabling targeted retries
  • POMTOC (L239) — Routed POMTOC Tideworks requests through a residential proxy and added required Referer/Origin headers to restore data collection
  • Free plan container limits — Free plan accounts now meter against active container concurrency rather than monthly cumulative counts, so picked-up and delivered containers no longer count toward the limit
  • Duplicate tags — Eliminated a race condition that could cause duplicate tag creation to fail with a unique constraint error
  • Postmark email intake — Recipient email lookups are now case-insensitive, fixing missed matches on inbound document emails
  • Pay-As-You-Go cancellation — Fixed handling of Stripe subscription period dates so the cancel response returns accurate end-of-period timing for newer subscription structures
  • Daily digest jobs — Database errors during daily digest delivery now release the cache lock cleanly so the next run can proceed
April 27, 2026
APIDashboard
Booking number type inference, delivered date filter, document fuzzy search, hold descriptions, and bug fixes

Booking number support in Infer Tracking Number

The Infer Tracking Number endpoint now predicts the carrier and number type for booking numbers, in addition to container numbers and bills of lading. Send a booking number you aren’t sure how to route, and Terminal49 returns a confidence-scored decision so you can create the tracking request with the correct VOCC SCAC and request_type.

Infer Tracking Number guide

How to use Infer Tracking Number in your workflow

Delivered date filter and column on the container dashboard

The container dashboard now includes a Delivered at column and date-range filter, plus delivered-date sorting. Quickly find recently delivered containers, sort by delivery date, or filter to a specific window for reporting and reconciliation.

Fuzzy search for documents

Document search is now fuzzy across shipment, container, and tracking request reference numbers. Minor typos, format differences, or partial reference numbers still return the right document, reducing time spent hunting for paperwork.

Hold descriptions on container holds

Each hold returned on a container now includes a plain-language description explaining what the hold means and what’s typically required to clear it. The descriptions are surfaced wherever holds appear so your team — and your customers — can act without looking up terminology.

Holds and fees guide

How to work with holds and fees data

Reference number flag on custom field definitions

Custom field definitions now support a reference_number flag. Mark a custom field as a reference number and Terminal49 will treat its value as a searchable identifier alongside built-in references like PO numbers and BOLs.

Custom Field Definitions

Custom Fields API reference

PO number normalization for document linking

Document-to-shipment linking via PO numbers now normalizes common format variants (separators, prefixes, and casing differences), so documents match shipments even when the PO is written slightly differently across systems.

Bug fixes

  • Containers requiring attention — Picked-up, on-rail, empty-returned, and delivered containers no longer appear under the “needs attention” LFD view. Only containers still active at a terminal show up
  • Tideworks fees — Containers reported as on a vessel or on rail no longer return stale terminal fees from a previous move
  • MSC Port of Discharge events — Improved criteria for selecting the correct POD arrival event on MSC shipments
  • LBCT inland transfers — Fixed handling of on-dock-to-inland transfer events at LBCT, so rail moves out of the terminal are tracked correctly
  • COSCO vessel departure — Improved logic for determining when a COSCO vessel has departed the port of loading
  • Vessel event deduplication — Fixed duplicate vessel events on the shipment timeline coming from carriers and from the CSE invalidation pipeline
  • Document linking race condition — Eliminated a race condition that could leave a document briefly unlinked when references arrived from multiple sources at once
  • Webhook notifications page — Fixed an exception that could occur when listing webhook notifications containing document processing events
  • Carrier integrations — Fixes to MAEU auth handling (now treats 403 correctly), APM Empty In OAuth requests, BNSF rail scraping, NSRR equipment requests, Hapag-Lloyd booking sweeps for shipments with no containers, and Voyager terminal request headers
  • Terminal data — Updated headers for SSAMX and Holt agent terminals, and added external location mapping for PCIU
  • Document email intake — Tightened sender-email rules so unrelated inbox messages are filtered out, and fixed an edge case where a single email recipient was not handled as an array
April 20, 2026
APIDashboard
Improved document linking, mark-as-delivered fix, LFD accuracy improvements, and terminal data fixes

Smarter document-to-shipment linking

Documents are now matched to shipments using indirect references such as purchase order (PO) numbers. Previously, a document had to contain a direct identifier like a bill of lading or container number. Now, if a document references a PO number that appears on another already-linked document, Terminal49 can connect the two — reducing unlinked documents and manual work.

Document processing guide

How document linking works

Improved document extraction accuracy

Document data extraction now uses the original filename as additional context, improving field-level accuracy when the filename contains shipment identifiers or document type hints.

Bug fixes

  • Mark as delivered — Fixed an issue where marking a container as delivered from the dashboard event viewer could fail. User-submitted delivery events are now accepted correctly
  • Stale terminal LFD dates — Fixed a bug where outdated Last Free Day dates from a previous cycle could appear on containers still in transit. Terminal LFD events are now rejected until the container arrives at the port
  • MSC departure events — Corrected incorrect departure-from-POD events being reported for certain MSC containers
  • Hapag-Lloyd tracking — Fixed an error that could occur when Hapag-Lloyd returns an empty shipment overview, preventing container data from loading
  • Norfolk Southern rail LFD timezone — Fixed incorrect timezone parsing for Norfolk Southern rail Last Free Day dates, which could shift the date by a day
  • Dashboard event viewer — Fixed display issues in the unified event viewer for user-submitted events
  • Terminal data collection — Resolved connectivity and data retrieval issues at Goport, Maher, and Packer Avenue terminals, restoring terminal-sourced hold, fee, and availability data for containers at those facilities
April 14, 2026
APIDashboard
Dashboard deep linking, calculated LFD, Smart LFD dashboard columns, and bug fixes

Dashboard deep linking

You can now link directly to any shipment or container in the Terminal49 dashboard using a container number, bill of lading, booking number, or reference number — no internal IDs needed.Use the URL pattern:
https://app.terminal49.com/shipments/find?q={identifier}
The link automatically resolves to the correct tracking page, making it easy to link from a TMS, ERP, spreadsheet, or automated notification.

Deep linking guide

How to build direct links to shipments and containers

Calculated Last Free Day

The Smart LFD system now includes a calculated Last Free Day derived from carrier demurrage tariff rules. When a shipping line or terminal hasn’t reported an LFD, Terminal49 computes one using the applicable tariff — including free days, start events, holidays, and business-day rules.Calculated values appear as a fallback in the import_deadlines field on the container API. If a reported LFD is available from the carrier or terminal, it takes priority.

Container API reference

View the container resource

Smart LFD dashboard columns

The container dashboard now includes two new columns for accounts with Smart LFD enabled:
  • Calc. Line LFD — the calculated Last Free Day derived from carrier tariff rules
  • Smart LFD — the best available LFD with its source displayed, so you can see at a glance whether the date comes from the shipping line, terminal, or a tariff calculation
Click the Smart LFD value to open a detail modal showing the full calculation breakdown, including tariff inputs, free days, and the day-by-day calendar.

Bug fixes

  • Hapag-Lloyd booking tracking — Fixed an issue where certain Hapag-Lloyd bookings could return an invalid number error, preventing container data from loading
April 2026
APIDashboard
Smart Last Free Day, inland destination ETA source transparency, and bug fixes

Smart Last Free Day

The container API now returns a detailed breakdown of Last Free Day (LFD) data within the import_deadlines field. Instead of a single date, you get separate LFD values from the shipping line and the terminal facility — at both the port of discharge and the inland destination.Each source includes:
  • Original — the first LFD reported
  • Current — the latest LFD reported
  • Calculated — a derived value when the raw date needs adjustment
A unified selection shows which source Terminal49 considers the best current LFD and why.

Container API reference

View the container resource

Inland destination ETA source transparency

Containers now include an inland_destination_eta_source_summary field that tells you exactly where the displayed inland destination ETA comes from. Possible sources are:
  • Shipping line — ETA provided by the carrier
  • Rail — ETA from the rail carrier
  • T49 operations team — manually verified ETA
  • T49 prediction engine — machine-learning-based estimate
The Terminal49 dashboard also shows the active ETA source, and hovering over it displays all available estimates so you can compare.

Expanded shipping line LFD coverage

Shipping line Last Free Day data is now collected from additional SSA terminals, improving LFD accuracy for containers moving through those facilities.

Container table properties

DataSync containers reference

Bug fixes

  • Hapag-Lloyd booking tracking — Fixed an error that could prevent booking equipment data from being returned for Hapag-Lloyd shipments
  • Dashboard copy/paste — Copy and paste keyboard shortcuts in the container dashboard no longer interfere with text input fields
  • Webhook notification links — The dashboard webhook notifications page now correctly displays reference links for events with multiple related resources
March 2026
APISDKMCPDataSync
TypeScript SDK, MCP server, Custom Fields API, webhook trigger endpoint, and DataSync improvements

TypeScript SDK

Released the Terminal49 TypeScript SDK (@terminal49/sdk), a typed client for Node.js 18+ with built-in retry logic, error handling, and JSON:API deserialization.
  • Track containers, retrieve shipments, and manage tracking requests with type-safe methods
  • Automatic retry with exponential backoff for rate limits and server errors
  • Flexible response formats: raw JSON:API, mapped objects, or both
npm install @terminal49/sdk

SDK docs

Get started with the TypeScript SDK

MCP server

Launched the Terminal49 MCP server, letting you query live container and shipment data from Claude Desktop, Cursor, or any MCP-compatible AI client.
  • 10 tools — search, track, get container details, shipment routing, transport events, and more
  • 3 prompts — pre-built workflows for tracking, demurrage analysis, and delay root cause analysis
  • Connect with a single config block — no custom code required

MCP setup guide

Connect your AI client to Terminal49

Custom Fields API

You can now create and manage custom fields on shipments and containers via the API. Define your own field schemas (text, number, date, single-select, multi-select), create option lists, and attach values to individual shipments or containers.
  • Custom Field Definitions — create, update, list, and delete field schemas scoped to shipments or containers
  • Custom Field Options — manage allowed values for select-type fields
  • Custom Fields — assign values to specific shipments or containers

Custom Field Definitions

View the Custom Fields API reference

Webhook trigger endpoint

Added POST /webhooks/trigger to send a one-time test webhook delivery to any HTTPS URL — without creating a webhook endpoint first. Use it to validate your webhook handler before going live.

Trigger a webhook

API reference for the trigger endpoint

DataSync improvements

  • Shipping line Last Free Day — new ssl_last_free_day_on and ssl_last_free_day_on_local columns on both the containers and containers_rail tables, so you can distinguish the shipping line’s LFD from the terminal’s LFD
  • Pending hold status — individual hold columns (freight_hold, customs_hold, usda_hold, tmf_hold, other_hold) now support a "Pending" value in addition to "Hold" and blank, giving you earlier visibility into holds before they become active

Container table properties

DataSync containers reference

Holds and fees guide

How to work with holds and fees data
February 2026
APIDataSync
Container Holds, Fees, and Release Readiness guide

Container Holds, Fees, and Release Readiness

Published a comprehensive guide for working with holds and fees data in the Terminal49 API. The guide covers:
  • Pickup readiness logic — a decision flowchart and code example showing how to combine available_for_pickup with holds_at_pod_terminal to determine if a container can be picked up
  • Hold and fee enum references — quick-reference tables for all hold names and fee types, with expandable details for each value
  • Webhook changeset examples — how to subscribe to container.updated and react to hold/fee changes in real time
  • Rail and inland destinations — clarification that the same fields apply at inland rail terminals, not just the port of discharge
  • FAQ — answers to common integration questions like double-counting fees, sync lag between holds and availability, and case-sensitive hold names

Read the guide

Container Holds, Fees, and Release Readiness
December 2025
API
Infer Tracking Number (Beta)

Infer Tracking Number (Beta)

Added the Infer Tracking Number endpoint to help you predict:
  • The VOCC SCAC to use for tracking
  • The number type (container, bill of lading, booking)
  • A confidence-driven decision (auto_select, needs_confirmation, no_prediction)

API Reference

Infer Tracking Number endpoint details

Guide

How to use Infer Tracking Number in your workflow
Use Infer Tracking Number when you have a valid tracking number but don’t know the correct VOCC SCAC.
December 2025
APIDataSync
Documentation improvements

Documentation improvements

Added an Updates section to publish API/DataSync changes.Added cross-links from relevant docs to Infer Tracking Number.