Blog
How to Track a Container Using API?
The old way to track containers
Big businesses that ship thousands of containers a year or even small businesses that ship a few containers a year often search for the best way to track all their containers.
There are of course several ways to track a container. One of the most common methods is to use the online tracking system that shipping company’s websites have. Some of the biggest companies out there include Evergreen, Maersk, MSC, etc. With each website handling their own container tracking system. You will need one of three things to track your container though.
What are the three things I can use to track a container with api?
Container Number (CN)
Each container has a unique container number – a combination of numbers and letters.
Bill of Lading (BOL)
A bill of lading (BL or BoL) is a legal document issued by a carrier (transportation company) to a shipper that details the type, quantity, and destination of the goods being carried.
Booking Number (BN)
Every shipping company has its own system for booking cargo space on a vessel. This system includes a unique booking number that is used to track and manage the shipment.
Now that you have one of the three examples mentioned above, you could visit the Company’s website that is handling your container and track it that way. This however can be a very daunting task. Having to track different containers across numerous different websites is time consuming and frustrating but…
What if we told you there was a much easier way to track all of your containers in a single place using api?
JSONCargo’s Container API will transform your business and give you an edge over your competitors. With our Maritime API you will have real-time container tracking of as many containers as you wish without having to manually track them over different websites. All your shipping and logistic needs in a single place.
The Container API can provide you with a wealth of extensive details.
| Parameter | Data Type | Description | Example Value |
|---|---|---|---|
| container_id | integer | Unique identifier for the container | ABC1234567 |
| container_type | string | Specifies the classification of a shipping container, indicating its size and purpose | DC/4H |
| container_status | string | Current status of the container | Import Truck Gate Out from Rail Ramp |
| tare | float | Represents the empty weight of the container without any cargo inside | 5691.6 |
| shipping_line_name | string | Name of the shipping line company | Hyundai Merchant Marine |
| shipping_line_id | integer | JSONCargo Internal identifier for the shipping line company | 0012 |
| shipped_from | string | Indicates the location or origin where the container was initially shipped from | YANTIAN, SHENZHEN, CHINA |
| shipped_from_terminal | string | Specifies the terminal at the origin where the container was loaded or dispatched | YANTIAN INT'L CONTAINER TERMINAL LTD. |
| shipped_to | string | Denotes the destination where the container is being shipped to | MEMPHIS, TN |
| shipped_to_terminal | string | Specifies the terminal at the destination where the container is scheduled to be unloaded or delivered | UNION PACIFIC RR |
| atd_origin | date time | Actual time of departure from the origin (Local time) | 2024-07-16 17:28 |
| eta_final_destination | date time | Estimated time of arrival at the final destination (Local time) | 2024-09-04 11:29 |
| last_location | string | The most recent location where the container was tracked | MEMPHIS, TN |
| last_location_terminal | string | The terminal of the most recent tracked location | UNION PACIFIC RR |
| next_location | string | The upcoming destination in the container’s journey | BUSAN, KOREA |
| next_location_terminal | string | The terminal at the next location where the container will arrive | BUSAN CONTAINER TERMINAL |
| atd_last_location | date time | Actual time of departure from the last known location (Local time) | 2024-07-28 16:54 |
| eta_next_destination | date time | Estimated time of arrival at the next destination (Local time) | 2024-07-28 16:54 |
| timestamp_of_last_location | date time | The date and time the container was last tracked at its previous location (Local time) | 2024-09-04 11:29 |
| last_movement_timestamp | date time | The date and time of the most recent recorded movement of the container (Local time) | 2024-09-05; 14:51 |
| loading_port | string | The port where the container was initially loaded onto the vesse | YANTIAN, SHENZHEN, CHINA |
| discharging_port | string | The port where the container is scheduled to be unloaded | LOS ANGELES, CA |
| bill_of_lading | string | The unique identifier or reference for the container’s shipment documentation | SZPM20235804 |
| last_vessel_name | string | The name of the last vessel the container was aboard. | TANGIER EXPRESS |
| last_voyage_number | string | The voyage number of the last vessel the container was on | 0054E |
| current_vessel_name | string | The name of the current vessel the container is aboard | HYUNDAI FORWARD |
| current_voyage_number | string | The voyage number of the current vessel carrying the container | 0157E |
| last_updated | date time | Time when JSONCargo last retrieved container information (YYYY-MM-DD; HH:MM in UTC) | 2024-09-13; 09:10 |
We’ve made it easy for you to automatically track and trace all your containers and keep all your maritime data in a single place.
Container API Setup in under 5 minutes
The best part is that you can setup your Container API in under 5 minutes with just three easy steps.
Automatize your container API data
As you can see, JSONCargo’s container API comes integrated with robust monitoring and logging tools to enhance your business and optimize your maritime operations, and with extended support and documentation to boot, you get all the advantages of taking your business to the next level.
