Ocean Network Express (ONE) Container Tracking API
JSONCargo container tracking API enables seamless tracking and tracing of containers handled by Ocean Network Express (ONE) shipping line.
Real-Time Container Monitoring
Track Containers as they move across oceans and ports. Worldwide full visibility into their transit status.
Key Data Points for 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 HMM, Hapag-Lloyd, Evergreen and more.
Major shipping line coverage
JSONCargo covers more than 95% of all carriers, so you can be confident that nearly every commercial container is included in 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 | Ocean Network Express |
| 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 ONE Tracking API
Get answers to commonly asked questions
The Ocean Network Express (ONE) Container Tracking API by JSONCargo is a real-time tracking service that allows businesses to trace containers shipped under the ONE carrier network.
It delivers end-to-end shipment visibility through a single API connection, enabling users to retrieve live status updates and schedule events.
With the ONE container tracking API, you can access detailed shipment data, including:
Official container identifier (container no.)
Equipment attributes and container specifications (size, dimensions, tare weight, type)
Cargo classification (e.g., dry container designation)
Port of loading, Port of discharge
Vessel details carrying the container, current schedule, and route progress
ETA updates
Operational history, such as gate-in, transshipment, holds, delays, and discharge activities
The container no. is required for tracking ONE container because:
ONE may register multiple containers under the same booking ref
The booking ref alone can refer to a shipment group, not a single container
The container no. uniquely identifies the equipment globally