# Terminal 49

## Docs

- [Edit a container](https://terminal49.com/docs/api-docs/api-reference/containers/edit-a-container.md): Update a container
- [Get a container](https://terminal49.com/docs/api-docs/api-reference/containers/get-a-container.md): Retrieves the details of a container.
- [Get a container's raw events](https://terminal49.com/docs/api-docs/api-reference/containers/get-a-containers-raw-events.md): #### Deprecation warning
The `raw_events` endpoint is provided as-is.

 For past events we recommend consuming `transport_events`.

---
Get a list of past and future (estimated) milestones for a container as reported by the carrier. Some of the data is normalized even though the API is called raw_events. 

Normalized attributes: `event` and `timestamp` timestamp. Not all of the `event` values have been normalized. You can expect the the events related to container movements to be normalized but there are cases where events are not normalized. 

For past historical events we recommend consuming `transport_events`. Although there are fewer events here those events go through additional vetting and normalization to avoid false positives and get you correct data.
- [Get a container's transport events](https://terminal49.com/docs/api-docs/api-reference/containers/get-a-containers-transport-events.md): Get a list of past transport events (canonical) for a container. All data has been normalized across all carriers. These are a verified subset of the raw events may also be sent as Webhook Notifications to a webhook endpoint.

This does not provide any estimated future events. See `container/:id/raw_events` endpoint for that.  
- [List containers](https://terminal49.com/docs/api-docs/api-reference/containers/list-containers.md): Returns a list of container. The containers are returned sorted by creation date, with the most recently refreshed containers appearing first.

This API will return all containers associated with the account.
- [Get a metro area using the un/locode or the id](https://terminal49.com/docs/api-docs/api-reference/metro-areas/get-a-metro-area-using-the-unlocode-or-the-id.md): Return the details of a single metro area.
- [null](https://terminal49.com/docs/api-docs/api-reference/parties/create-a-party.md): Creates a new party
- [null](https://terminal49.com/docs/api-docs/api-reference/parties/edit-a-party.md): Updates a party
- [null](https://terminal49.com/docs/api-docs/api-reference/parties/get-a-party.md): Returns a party by it's given identifier
- [null](https://terminal49.com/docs/api-docs/api-reference/parties/list-parties.md): Get a list of parties
- [Get a port using the locode or the id](https://terminal49.com/docs/api-docs/api-reference/ports/get-a-port-using-the-locode-or-the-id.md): Return the details of a single port.
- [Edit a shipment](https://terminal49.com/docs/api-docs/api-reference/shipments/edit-a-shipment.md): Update a shipment
- [Get a shipment](https://terminal49.com/docs/api-docs/api-reference/shipments/get-a-shipment.md): Retrieves the details of an existing shipment. You need only supply the unique shipment `id` that was returned upon `tracking_request` creation.
- [List shipments](https://terminal49.com/docs/api-docs/api-reference/shipments/list-shipments.md): Returns a list of your shipments. The shipments are returned sorted by creation date, with the most recent shipments appearing first.

This api will return all shipments associated with the account. Shipments created via the `tracking_request` API aswell as the ones added via the dashboard will be retuned via this endpoint. 
- [Resume tracking a shipment](https://terminal49.com/docs/api-docs/api-reference/shipments/resume-tracking-shipment.md): Resume tracking a shipment.  Keep in mind that some information is only made available by our data sources at specific times, so a stopped and resumed shipment may have some information missing.
- [Stop tracking a shipment](https://terminal49.com/docs/api-docs/api-reference/shipments/stop-tracking-shipment.md): We'll stop tracking the shipment, which means that there will be no more updates.  You can still access the shipment's previously-collected information via the API or dashboard.

You can resume tracking a shipment by calling the `resume_tracking` endpoint, but keep in mind that some information is only made available by our data sources at specific times, so a stopped and resumed shipment may have some information missing.
- [Get a single shipping line](https://terminal49.com/docs/api-docs/api-reference/shipping-lines/get-a-single-shipping-line.md): Return the details of a single shipping line.
- [Shipping Lines](https://terminal49.com/docs/api-docs/api-reference/shipping-lines/shipping-lines.md): Return a list of shipping lines supported by Terminal49. 
N.B. There is no pagination for this endpoint.
- [Get a terminal using the id](https://terminal49.com/docs/api-docs/api-reference/terminals/get-a-terminal-using-the-id.md): Return the details of a single terminal.
- [Create a tracking request](https://terminal49.com/docs/api-docs/api-reference/tracking-requests/create-a-tracking-request.md): To track an ocean shipment, you create a new tracking request. 
Two attributes are required to track a shipment. A `bill of lading/booking number` and a shipping line `SCAC`. 

Once a tracking request is created we will attempt to fetch the shipment details and it's related containers from the shipping line. If the attempt is successful we will create in new shipment object including any related container objects. We will send a `tracking_request.succeeded` webhook notification to your webhooks.  

If the attempt to fetch fails then we will send a `tracking_request.failed` webhook notification to your `webhooks`.  

A `tracking_request.succeeded` or `tracking_request.failed` webhook notificaiton will only be sent  if you have  atleast one active webhook. 
- [Edit a tracking request](https://terminal49.com/docs/api-docs/api-reference/tracking-requests/edit-a-tracking-request.md): Update a tracking request
- [Get a single tracking request](https://terminal49.com/docs/api-docs/api-reference/tracking-requests/get-a-single-tracking-request.md): Get the details and status of an existing tracking request. 
- [List tracking requests](https://terminal49.com/docs/api-docs/api-reference/tracking-requests/list-tracking-requests.md): Returns a list of your tracking requests. The tracking requests are returned sorted by creation date, with the most recent tracking request appearing first.
- [Get a vessel using the id](https://terminal49.com/docs/api-docs/api-reference/vessels/get-a-vessel-using-the-id.md): Returns a vessel by it's given identifier
- [Get a vessel using the imo](https://terminal49.com/docs/api-docs/api-reference/vessels/get-a-vessel-using-the-imo.md): Returns a vessel by the given IMO number.
- [Get a single webhook notification](https://terminal49.com/docs/api-docs/api-reference/webhook-notifications/get-a-single-webhook-notification.md): 

- [Get webhook notification payload examples](https://terminal49.com/docs/api-docs/api-reference/webhook-notifications/get-webhook-notification-payload-examples.md): Returns an example payload as it would be sent to a webhook endpoint for the provided `event` 
- [List webhook notifications](https://terminal49.com/docs/api-docs/api-reference/webhook-notifications/list-webhook-notifications.md): Return the list of  webhook notifications. This can be useful for reconciling your data if your endpoint has been down. 
- [Create a webhook](https://terminal49.com/docs/api-docs/api-reference/webhooks/create-a-webhook.md): You can configure a webhook via the API to be notified about events that happen in your Terminal49 account. These events can be realted to tracking_requests, shipments and containers. 

This is the recommended way tracking shipments and containers via the API. You should use this instead of polling our the API periodically.  
- [Delete a webhook](https://terminal49.com/docs/api-docs/api-reference/webhooks/delete-a-webhook.md): Delete a webhook
- [Edit a webhook](https://terminal49.com/docs/api-docs/api-reference/webhooks/edit-a-webhook.md): Update a single webhook
- [Get single webhook](https://terminal49.com/docs/api-docs/api-reference/webhooks/get-single-webhook.md): Get the details of a single webhook
- [List webhook IPs](https://terminal49.com/docs/api-docs/api-reference/webhooks/list-webhook-ips.md): Return the list of IPs used for sending webhook notifications.  This can be useful for whitelisting the IPs on the firewall.
- [List webhooks](https://terminal49.com/docs/api-docs/api-reference/webhooks/list-webhooks.md): Get a list of all the webhooks
- [3. List Your Shipments & Containers](https://terminal49.com/docs/api-docs/getting-started/list-shipments-and-containers.md)
- [4. How to Receive Status Updates](https://terminal49.com/docs/api-docs/getting-started/receive-status-updates.md)
- [1. Start Here](https://terminal49.com/docs/api-docs/getting-started/start-here.md)
- [2. Tracking Shipments & Containers](https://terminal49.com/docs/api-docs/getting-started/tracking-shipments-and-containers.md): Submitting a tracking request is how you tell Terminal49 to track a shipment for you.
- [How to add a Customer to a Tracking Request?](https://terminal49.com/docs/api-docs/in-depth-guides/adding-customer.md)
- [Event Timestamps](https://terminal49.com/docs/api-docs/in-depth-guides/event-timestamps.md)
- [Including Resources](https://terminal49.com/docs/api-docs/in-depth-guides/including-resources.md)
- [Quick Start Guide](https://terminal49.com/docs/api-docs/in-depth-guides/quickstart.md)
- [Integrate Rail Container Tracking Data](https://terminal49.com/docs/api-docs/in-depth-guides/rail-integration-guide.md): This guide provides a comprehensive, step-by-step approach for integrating North American Class-1 rail container tracking data into your systems. Whether you are a shipper or a logistics service provider, this guide will help you track all your rail containers via a single API.
- [Terminal49 Map Embed Guide](https://terminal49.com/docs/api-docs/in-depth-guides/terminal49-map.md): The Terminal49 Map allows you to embed real-time visualized container tracking on your website with just a few lines of code.
- [Tracking Widget Embed Guide](https://terminal49.com/docs/api-docs/in-depth-guides/terminal49-widget.md): The Terminal49 Track & Trace Widget allows you to embed real-time container tracking on your website with just a few lines of code. This widget provides a seamless user experience and helps improve customer satisfaction.
- [Tracking Request Lifecycle](https://terminal49.com/docs/api-docs/in-depth-guides/tracking-request-lifecycle.md)
- [Webhooks](https://terminal49.com/docs/api-docs/in-depth-guides/webhooks.md)
- [API Data Sources and Availability.](https://terminal49.com/docs/api-docs/useful-info/api-data-sources-availability.md): Our platform gets data from variety of sources in order to create a complete view of a shipment and containers. However,some data is not universally available from all sources, and some data does not become available until certain milestones pass. This page will help you understand which data sources we support, and which data items should be universally expected by your code and which you need to code more defensively around.
- [Pricing](https://terminal49.com/docs/api-docs/useful-info/pricing.md)
- [Test Numbers](https://terminal49.com/docs/api-docs/useful-info/test-numbers.md)
- [Tracking Request Retrying](https://terminal49.com/docs/api-docs/useful-info/tracking-request-retrying.md)
- [Webhook Events Examples](https://terminal49.com/docs/api-docs/useful-info/webhook-events-examples.md)
- [Terminal49 Dev Documentation](https://terminal49.com/docs/datasync/home.md)
- [Overview](https://terminal49.com/docs/datasync/overview.md)
- [Supported Destinations](https://terminal49.com/docs/datasync/supported-destinations.md)
- [Containers (deprecated)](https://terminal49.com/docs/datasync/table-properties/containers.md)
- [Containers](https://terminal49.com/docs/datasync/table-properties/containers_rail.md)
- [Shipments](https://terminal49.com/docs/datasync/table-properties/shipments.md)
- [Tracking Requests](https://terminal49.com/docs/datasync/table-properties/tracking-requests.md)
- [Transfer Status](https://terminal49.com/docs/datasync/table-properties/transfer-status.md)
- [Transport Events](https://terminal49.com/docs/datasync/table-properties/transport-events.md)
- [Terminal49 Dev Documentation](https://terminal49.com/docs/home.md)


## Optional

- [Contact](https://www.terminal49.com/contact/)
- [Schedule Demo](https://www.terminal49.com/demo/)
- [Blog](https://www.terminal49.com/blog/)