Cosco Container Tracking API
JSONCargo container tracking API allows you to track & trace Containers from the Cosco shipping lines.
Real-Time Container Monitoring
Track COSCO containers worldwide as they move across oceans and ports. Get full visibility into container location, status, and transit updates.
Key Data Points for Cosco Containers
Get Key Data into your Container transit status, such as ETA, ATD, last location, loading port, discharging port and more.
Major Shipping Lines Coverage
Track your containers in a single platform. JSONCargo has coverage with major shipping lines like Cosco, Maersk, Hapag-Lloyd, ONE, and more.
Major shipping line coverage
JSONCargo covers more than 95% of all shipping lines, so you can be sure that practically all commercial containers are in our API database.
Cosco Container Tracking API Data Table
| 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 | China Ocean Shipping Company |
| shipping_line_id | integer | JSONCargo Internal identifier for the shipping line company | 0015 |
| 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 |
Cosco Container Prefix List
This is what we cover for Cosco container prefixes:
| Prefix | |
|---|---|
CCLU | OERU |
CSNU | BMOU |
CBHU | FBIU |
CSLU | DFSU |
BSDU | SZLU |
LZTU | TTNU |
VECU | FCIU |
YZTU | TEMU |
CVTU | UETU |
TIIU | FFAU |
TRHU | TGBU |
OOCU | BEAU |
OOLU | MAGU |
CAIU | TCKU |
FSCU | CAAU |
Get Real-Time Container Tracking data
Our container tracking API enables proactive delay management and performance optimization to keep your supply chain on track.
Container location
{
Track Containers Anywhere with Real-Time GPS
}
Departure and arrival ports
{
Trace Containers from Port to Arrival with Real-Time Tracking
}
Detailed container insights
{
Access Container History, Status, Vessel Info, and More
}
Your container API key in 3 steps
{
Setup in 5 Minutes: Subscribe, Pay, Get API Key, and Integrate
}
Frequently Asked Questions about COSCO Tracking API
Get answers to commonly asked questions
The COSCO Container Tracking API by JSONCargo allows users to track containers from the COSCO shipping line in real time.
It provides real-time tracking of Cosco containers, including status, location, and shipment milestones.
Yes, JSONCargo supports multi-carrier container tracking, enabling you to monitor containers from major carriers such as Maersk, CMA CGM, Hapag-Lloyd, and ZIM in one platform. This unified approach saves time and simplifies global shipment management.
COSCO Container Tracking data refreshes each time a request is made to our database. While accuracy is high, occasional delays may happen due to port congestion or temporary reporting gaps.
Access is provided via secure API keys.
Getting an API key is simple. Subscribe to the JSONCargo service, complete the payment, and receive your API key. You can then integrate it into your system. The API uses standard REST endpoints and allows developers to easily embed tracking data into logistics platforms, dashboards, or mobile applications.