mintlify · Oct 26, 2026
@@ -1,5 +1,5 @@
 ---
-title: "List Shipments and Containers"
+title: "List shipments and containers"
 sidebarTitle: "3. List Shipments & Containers"
 description: "List tracked shipments and containers via the Terminal49 API, filter results by status, and retrieve the tracking data your integration needs."
 keywords:
@@ -257,7 +257,7 @@ curl "https://api.terminal49.com/v2/containers" \
   -H "Authorization: Token YOUR_API_KEY"
 ```
 
-We suggest copying the response into a text editor so you can examine it while continuing the tutorial.
+Copy the response into a text editor so you can examine it while you continue the tutorial.
 
 ## Anatomy of containers JSON response
 

@@ -37,7 +37,7 @@ To use the dashboard:
     Go to [Developer Webhooks](https://app.terminal49.com/developers/webhooks) in your Terminal49 dashboard.
   </Step>
   <Step title="Create the endpoint">
-    Click **Create Webhook Endpoint** and enter your HTTPS endpoint URL.
+    Select **Create Webhook Endpoint** and enter your HTTPS endpoint URL.
   </Step>
   <Step title="Select events and save">
     Select the events you want to receive, then save the webhook.

@@ -1,5 +1,5 @@
 ---
-title: "Open the TypeScript SDK Quickstart"
+title: "Open the TypeScript SDK quickstart"
 description: "Redirect page for the Terminal49 TypeScript SDK quickstart. Track a container and retrieve live shipment data in a few lines of code."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "Start Here: Track Shipments with the Terminal49 API"
+title: "Start here: Track shipments with the Terminal49 API"
 sidebarTitle: "1. Start Here"
 description: "Set up Terminal49 API access, generate an API key, and make your first tracking request to start monitoring ocean shipments and containers."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Track Shipments and Containers"
+title: "Track shipments and containers"
 sidebarTitle: "2. Tracking Shipments & Containers"
 description: "Create tracking requests for bill of lading, booking, and container numbers in the Terminal49 API and start receiving shipment milestone updates."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Add a Customer to a Tracking Request"
+title: "Add a customer to a tracking request"
 description: "Associate a customer party with a Terminal49 tracking request so new shipments automatically inherit the correct party relationship and metadata."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Assign Shipper, Consignee, and Other Parties"
+title: "Assign shipper, consignee, and other parties"
 description: "Set the shipper, consignee, freight forwarder, notify party, customs broker, or dray carrier on shipments and containers through the Terminal49 API."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 Container Statuses"
+title: "Terminal49 container statuses"
 description: "Understand every Terminal49 container status value, from on-ship to empty-returned, so your integration can interpret each shipment lifecycle stage."
 keywords:
   - "Terminal49 API"
@@ -41,7 +41,7 @@ The API returns the raw backend value (for example `grounded`). The Terminal49 d
 ### on_ship
 **Dashboard label: "On Ship"**
 
-**In transit by vessel** — The container is on a vessel. In the lifecycle this status first appears when the container is loaded or the vessel departs the port of lading, and it persists through the ocean voyage until the container is discharged at the Port of Discharge (POD).
+**In transit by vessel** — The container is on a vessel. This status first appears when the container is loaded or the vessel departs the port of lading. It persists through the ocean voyage until the container is discharged at the Port of Discharge (POD).
 
 Triggered by the *vessel loaded* or *vessel departed* milestone (and kept by subsequent on-vessel milestones such as *vessel arrived*, *vessel berthed*, and transshipment events).
 
@@ -83,7 +83,7 @@ While a hold is in place, the terminal will not release the container for pickup
 ### off_dock
 **Dashboard label: "Available at Shippers"**
 
-**At an off-dock facility** — The terminal reported that the container has moved off the main terminal to an off-dock or shipper's-own yard, where it's available for pickup. When this happens, Terminal49 attempts to identify the off-dock facility and re-point tracking to it, so this status can also appear briefly during that transition before status is pulled from the new facility. This value comes from terminal data (not the steamship line) and is uncommon.
+**At an off-dock facility** — The terminal reported that the container has moved off the main terminal to an off-dock or shipper's-own yard, where it's available for pickup. When this happens, Terminal49 attempts to identify the off-dock facility and re-point tracking to it. This status can also appear briefly during that transition, before Terminal49 pulls status from the new facility. This value comes from terminal data (not the steamship line) and is uncommon.
 
 ### picked_up
 **Dashboard label: "Picked up"**
@@ -93,7 +93,7 @@ While a hold is in place, the terminal will not release the container for pickup
 ### delivered
 **Dashboard label: "Delivered"**
 
-**Delivery confirmed** — The container has been delivered to the warehouse. This status is only set when delivery is [manually marked as delivered](https://help.terminal49.com/articles/4713318249-how-to-mark-containers-as-delivered) through the Terminal49 dashboard, because delivery date/time data is only available to the customer (Terminal49 does not have access to it).
+**Delivery confirmed** — The container has been delivered to the warehouse. This status is only set when you [manually mark the container as delivered](https://help.terminal49.com/articles/4713318249-how-to-mark-containers-as-delivered) in the Terminal49 dashboard. Delivery date and time data is only available to you, so Terminal49 does not have access to it.
 
 ### empty_returned
 **Dashboard label: "Empty Returned"**

@@ -1,5 +1,5 @@
 ---
-title: "Direct Links to Shipments and Containers"
+title: "Direct links to shipments and containers"
 sidebarTitle: "Tracking Page Links"
 description: "Link directly to a shipment or container tracking page using container numbers, BOL numbers, or references — no internal IDs needed."
 keywords:
@@ -12,7 +12,7 @@ keywords:
   - "tracking page links"
 ---
 
-You can link directly to any shipment or container in Terminal49 using an identifier you already have — a container number, bill of lading, booking number, or any reference number you've attached to a shipment. The link resolves to the correct tracking page automatically, so your team doesn't need to know Terminal49's internal UUIDs. This is especially useful when linking from a TMS, ERP, spreadsheet, internal tool, or automated notification.
+You can link directly to any shipment or container in Terminal49 using an identifier you already have. This can be a container number, bill of lading, booking number, or any reference number you've attached to a shipment. The link resolves to the correct tracking page automatically, so your team doesn't need to know Terminal49's internal UUIDs. This is especially useful when linking from a TMS, ERP, spreadsheet, internal tool, or automated notification.
 
 ## URL format
 

@@ -1,5 +1,5 @@
 ---
-title: "Direct Upload for Documents"
+title: "Direct upload for documents"
 sidebarTitle: "Direct Upload for Documents"
 description: "Upload files with the Terminal49 direct upload flow, retrieve a signed_id, and create document resources linked to your shipments or containers."
 keywords:

@@ -59,7 +59,7 @@ All API calls require an API key passed as a Bearer token:
 Authorization: Token YOUR_API_KEY
 ```
 
-To get your API key, go to **User > Developers > API Keys** (click your username in the bottom-left corner of the navigation). For more detail, see [Start Here](/api-docs/getting-started/start-here).
+To get your API key, go to **User > Developers > API Keys** (select your username in the bottom-left corner of the navigation). For more detail, see [Start Here](/api-docs/getting-started/start-here).
 
 ## Subscribing to events
 
@@ -86,10 +86,10 @@ curl -X POST https://api.terminal49.com/v2/webhooks \
 
 You can also configure webhooks from the Terminal49 dashboard:
 
-1. Click your username in the bottom-left corner of the navigation.
+1. Select your username in the bottom-left corner of the navigation.
 2. Go to **User > Developers > Webhooks**.
-3. To add a new endpoint, click **Create Webhook**, fill in your URL, and select the relevant events under **Document Events**.
-4. To update an existing endpoint, click into it and toggle on the document events you need.
+3. To add a new endpoint, select **Create Webhook**, fill in your URL, and select the relevant events under **Document Events**.
+4. To update an existing endpoint, open it and toggle on the document events you need.
 
 ## Webhook endpoint requirements
 

@@ -1,5 +1,5 @@
 ---
-title: "Event Timestamps"
+title: "Event timestamps"
 description: "Learn how Terminal49 stores transport event timestamps in UTC and how to convert them to local time using the matching IANA timezone field."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Container Holds, Fees, and Release Readiness"
+title: "Container holds, fees, and release readiness"
 description: "Determine when an import container is released for pickup by reading holds, fees, last free day, and availability data from the Terminal49 API."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 API Quickstart"
+title: "Terminal49 API quickstart"
 sidebarTitle: "Quick Start Guide"
 description: "Follow the Terminal49 API quickstart to create a tracking request, monitor your first shipment, and retrieve live container and shipment data."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Rate Limiting"
+title: "Rate limiting"
 description: "Understand Terminal49 API rate limits, HTTP 429 responses, and how to design clients that handle throttling with retries and exponential backoff."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Vessel and Container Route Data"
+title: "Vessel and container route data"
 description: "Access detailed container route segments and vessel position data from the Terminal49 API to build richer map and shipment visibility experiences."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 Map Embed Guide"
+title: "Terminal49 map embed guide"
 description: "Embed the Terminal49 container map in your website with a publishable API key to display live vessel positions and shipment location data."
 keywords:
   - "Terminal49 API"
@@ -147,7 +147,7 @@ The styles are written in [BEM](https://getbem.com/) style as well as they're sc
 
 ### Sizing
 
-By default, the map takes the full width of its container and some height. To expand the map, click the expand button in the bottom-left corner of the map.
+By default, the map takes the full width of its container and some height. To expand the map, select the expand button in the bottom-left corner of the map.
 You can also override the default styles to customize the map to your liking.
 
 For example, to tell the map to take 60% of the total viewport size when expanded, do the following:

@@ -31,7 +31,7 @@ Use the [List Webhook Events](/api-docs/api-reference/webhooks/list-webhook-even
 
 You can create a webhook from the dashboard or API.
 
-To use the dashboard, open [Developer Webhooks](https://app.terminal49.com/developers/webhooks) and click **Create Webhook Endpoint**.
+To use the dashboard, open [Developer Webhooks](https://app.terminal49.com/developers/webhooks) and select **Create Webhook Endpoint**.
 
 To use the API:
 
@@ -172,7 +172,7 @@ curl -s "https://api.terminal49.com/v2/webhook_notifications" \
   -H "Content-Type: application/vnd.api+json"
 ```
 
-Missed notifications cannot be replayed. After you fix the consumer, use [Trigger a Webhook](/api-docs/api-reference/webhooks/trigger-a-webhook) to re-test your handler with a sample payload, then re-fetch the affected shipments and containers from the REST API to backfill any missed state changes.
+Missed notifications cannot be replayed. After you fix the consumer, use [Trigger a Webhook](/api-docs/api-reference/webhooks/trigger-a-webhook) to re-test your handler with a sample payload. Then re-fetch the affected shipments and containers from the REST API to backfill any missed state changes.
 
 For more help, see [How to Troubleshoot Missing Webhook Notifications](https://help.terminal49.com/en/articles/7851422-missing-webhook-notifications).
 

@@ -1,5 +1,5 @@
 ---
-title: "Entitlements and Paid Features"
+title: "Entitlements and paid features"
 description: "Understand which Terminal49 API, map, widget, vessel, rail, and MCP features require additional account enablement and what non-entitled callers receive."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 API Pricing"
+title: "Terminal49 API pricing"
 description: "Review Terminal49 API pricing plans and find resources for evaluating access to ocean shipment and container tracking data for your integration."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 Test Tracking Numbers"
+title: "Terminal49 test tracking numbers"
 description: "Use Terminal49 test tracking numbers to simulate successful, failed, and edge-case tracking request outcomes when validating your sandbox integration."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 Webhook Event Examples"
+title: "Terminal49 webhook event examples"
 description: "Review sample Terminal49 webhook payloads for shipment, container, and tracking request events to build, test, and debug your webhook consumer."
 keywords:
   - "Terminal49 API"

@@ -1,5 +1,5 @@
 ---
-title: "Why Webhooks"
+title: "Why webhooks"
 sidebarTitle: "Overview"
 description: "Terminal49 is event-driven. Use webhooks to receive real-time shipment and container tracking updates instead of polling the REST API for changes."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Webhook Payloads"
+title: "Webhook payloads"
 sidebarTitle: "Payloads"
 description: "Reference for the Terminal49 webhook notification envelope, JSON:API included resource patterns, and links to complete event payload examples."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Monitor ETA Changes with Webhooks"
+title: "Monitor ETA changes with webhooks"
 sidebarTitle: "ETA Monitoring"
 description: "Subscribe to Terminal49 ETA change webhook events and alert your team automatically when a shipment's estimated arrival date or port of discharge shifts."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Alert on LFD Changes and Container Availability"
+title: "Alert on LFD changes and container availability"
 sidebarTitle: "LFD & Availability Alerts"
 description: "Use Terminal49 webhooks to monitor Last Free Day changes and container availability so you can dispatch pickups before demurrage charges begin."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 DataSync Documentation"
+title: "Terminal49 DataSync documentation"
 sidebarTitle: "DataSync Home"
 description: "Learn how Terminal49 DataSync delivers shipment, container, and transport event data into your data warehouse, database, or spreadsheet automatically."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "DataSync Overview"
+title: "DataSync overview"
 sidebarTitle: "Overview"
 description: "See how Terminal49 DataSync syncs shipment, container, and tracking request data into your existing data warehouse, database, or spreadsheet systems."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "DataSync Supported Destinations"
+title: "DataSync supported destinations"
 description: "See which databases, data warehouses, object stores, and spreadsheets Terminal49 DataSync supports as sync destinations for your tracking data."
 keywords:
   - "Terminal49 DataSync"

@@ -1,5 +1,5 @@
 ---
-title: "Deprecated DataSync Containers Table"
+title: "Deprecated DataSync containers table"
 sidebarTitle: "Containers (deprecated)"
 description: "Reference the deprecated Terminal49 DataSync containers table schema. Migrate to the current rail-aware containers table for new and existing integrations."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Containers Table"
+title: "Containers table"
 sidebarTitle: "Containers"
 description: "Reference the Terminal49 DataSync containers table schema, including rail-aware tracking fields, column definitions, data types, and relationships."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Shipments Table"
+title: "Shipments table"
 sidebarTitle: "Shipments"
 description: "Reference the Terminal49 DataSync shipments table schema, including column definitions, relationships to containers, and shipment-level tracking fields."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 SDK Error Handling"
+title: "Terminal49 SDK error handling"
 sidebarTitle: "Error Handling"
 description: "Catch and handle Terminal49 TypeScript SDK errors, including API validation failures and network timeouts, so your integration recovers gracefully."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 SDK Filtering and Pagination"
+title: "Terminal49 SDK filtering and pagination"
 sidebarTitle: "Filtering & Pagination"
 description: "Use canonical, validated shipment and container filters, explicit date bounds, party matching, and bounded pagination in the TypeScript SDK."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 SDK Methods Reference"
+title: "Terminal49 SDK methods reference"
 sidebarTitle: "Methods Reference"
 description: "Review every Terminal49 TypeScript SDK method organized by resource — shipments, containers, tracking requests, webhooks, and more — with usage examples."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "Terminal49 SDK Quickstart"
+title: "Terminal49 SDK quickstart"
 sidebarTitle: "Quickstart"
 description: "Install the Terminal49 TypeScript SDK, track a container, list shipments, and retrieve live tracking data in a few minutes with working examples."
 keywords:

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Authentication"
+title: "TypeScript SDK authentication"
 description: "Redirects to the Terminal49 TypeScript SDK authentication guide. Learn how to configure your API key and authenticate all SDK requests securely."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Methods Reference"
+title: "TypeScript SDK methods reference"
 description: "Redirects to the Terminal49 TypeScript SDK methods reference. Browse all available client methods for shipments, containers, and tracking requests."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Error Handling"
+title: "TypeScript SDK error handling"
 description: "Redirects to the Terminal49 TypeScript SDK error handling guide. Learn how to catch API errors, network timeouts, and validation failures."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Filtering"
+title: "TypeScript SDK filtering"
 description: "Redirects to the Terminal49 TypeScript SDK filtering guide. Learn how to filter shipments and containers by status, carrier, date, and other fields."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Installation"
+title: "TypeScript SDK installation"
 description: "Redirects to the Terminal49 TypeScript SDK installation guide. Install the SDK package from npm and configure it for your Node.js or TypeScript project."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Pagination"
+title: "TypeScript SDK pagination"
 description: "Redirects to the Terminal49 TypeScript SDK pagination guide. Learn how to paginate large result sets when listing shipments, containers, or events."
 keywords:
   - "Terminal49 SDK"

@@ -1,5 +1,5 @@
 ---
-title: "TypeScript SDK Quickstart"
+title: "TypeScript SDK quickstart"
 description: "Redirects to the Terminal49 TypeScript SDK quickstart. Get started tracking containers and retrieving shipment data in minutes with working examples."
 keywords:
   - "Terminal49 SDK"