HMM Container Tracking API
JSONCargo container tracking API allows you to track & trace Containers from Hyundai Merchant Marine (HMM) shipping line.
Real-Time Container Visibility
Track HMM Containers as they move across oceans and ports. Worldwide full visibility into their transit status.
Key HMM Container Data
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 Maersk, Hapag-Lloyd, ONE and more.
Major shipping line coverage
JSONCargo covers more than 95% of all shipping market, with that you can be sure that practically all commercial containers are in our API database
HMM Container 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 | 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 |
HMM Container Prefix List
This is what we cover for HMM container prefixes:
| Prefix |
|---|
HDMU |
HMMU |
KOCU |
GHMU |
HDGU |
HMRU |
CAAU |
Obtain Real-Time Container Tracking Data
Our container tracking API helps you foresee delays and optimize performance. It provides quick, intelligent tracking to keep your supply chain running smoothly
Optimized Shipment Visibility
{
JSONCargo provides real-time visibility into every HMM container with live tracking updates on port movements, vessel details, and schedule changes.
}
Easy API Integration
{
Easily connect JSONCargo’s API with ERP, TMS, or warehouse systems to automate container tracking updates and reduce manual work.
}
Simplified B/L and Container Number Tracking
{
Retrieve all containers linked to a single Bill of Lading in one place, ensuring faster verification and accurate shipment documentation.
}
Enhanced Integrated Logistics Planning
{
Use real-time data and automation to forecast delays, optimize delivery, and streamline logistics operations efficiently.
}
Frequently Asked Questions about HMM Container Tracking API
Get answers to commonly asked questions
JSONCargo’s HMM Container Tracking API provides live updates on container movements, vessel details, ETA, and port locations, ensuring complete shipment visibility.
Yes, JSONCargo supports easy API integration with ERP, TMS, and WMS platforms, allowing automatic synchronization of container tracking data.
Absolutely. You can use the API to retrieve all containers associated with a specific Bill of Lading, simplifying documentation and customs processes.
Yes, JSONCargo supports multi-carrier container tracking for major lines like Maersk, MSC, CMA CGM, ZIM, and Hapag-Lloyd through one unified API.
JSONCargo uses real-time tracking and data insights to help shippers optimize performance and gain better control over their supply chain.