Yang Ming Container Tracking API
The JSONCargo container tracking API allows efficient tracking and real-time monitoring of containers operated by Yang Ming Integrated Shipping Services.
See how it works
Real-Time Container Monitoring
Track Yang Ming containers as they move across oceans and ports, with full global visibility into their transit status.
Essential Tracking Data for Yang Ming 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 MSC, HMM, CMA CGM and more.
Major shipping line coverage
JSONCargo captures more than 95% of worldwide shipping movements, giving you reliable access to almost every commercial container through our API
Container Tracking API Data Table
| Parameter | Data Type | Description | Example Value |
|---|---|---|---|
| container_id | integer | Unique identifier for the container | DKF1234567 |
| container_type | string | Specifies the classification of a shipping container, indicating its size and purpose | 40'DRY HC. |
| container_status | string | Current status of the container | Empty Container Returned from Customer |
| 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 | Yang Ming Marine Transport Corporation |
| shipping_line_id | integer | JSONCargo Internal identifier for the shipping line company | 0013 |
| shipped_from | string | Indicates the location or origin where the container was initially shipped from | SANTOS, BR |
| shipped_from_terminal | string | Specifies the terminal at the origin where the container was loaded or dispatched | BRASIL TERMINAL PORTUARIO S/A |
| 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 |
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 Yang Ming Tracking API
Get answers to commonly asked questions
The Yang Ming Container Tracking API provided by JsonCargo enables container tracking through a developer-friendly API. Responses return a logistics event including operational milestones such as discharged at POD, gate in full, and gate out full. As well as ETA, along with cargo insights.
Data is delivered in JSON format.
You can track by:
Container number (e.g., YMMU1234567)
Bill of Lading number (YML B/L)
Yes. One B/L query can return events for all containers linked to it, allowing multi-container tracking in one API call.
Common milestones when it comes to container tracking may include:
discharged at pod
gate in full
gate out full
Port terminal operations may appear as:
Gate In Full → full container enters the terminal yard
Gate Out Full → full container exits the terminal
Events are pushed when the carrier/terminal publishes them, enabling real-time updates without fixed polling intervals.
The API does not support tracking a shipment portfolio as a single identifier.
Tracking is available per container number or per Bill of Lading (B/L). When you track a B/L, the API will return all containers linked to that B/L, including their timeline of shipment milestones and events.