MSC Container Tracking API
JSONCargo container tracking API allows you to track & trace Containers from MSC shipping line.
Container Location in Real Time
Track MSC Containers as they move across oceans and ports. Worldwide full visibility into their transit status.
Key MSC 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 all your containers in one place. JSONCargo supports major shipping lines including ZIM, Hapag-Lloyd, Evergreen, and others.
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
MSC Container 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 | 20' DRY VAN |
| container_status | string | Current status of the container | Gate in |
| 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 | Mediterranean 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 | 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 |
MSC Container Prefix List
This is what we cover for MSC container prefixes:
| Prefix | |
|---|---|
MSCU | MSRU |
MEDU | MSVU |
MSDU | CAIU |
MSMU | FCIU |
GTIU | FFAU |
MSNU | BEAU |
MSPU | TTNU |
MSTU | TRLU |
MSYU | TRIU |
MSZU | SZLU |
MADU | OTPU |
MSBU | FRB0 |
MSGU | EMU9 |
MSRU | CRXU |
MSVU | CRSU |
CAIU | CRLU |
FCIU | CHIU |
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
Transforming MSC Container Tracking
{
JSONCargo makes MSC container tracking effortless with real-time visibility, global data coverage, and automated updates. Follow every shipment from loading to delivery with complete accuracy.
}
Real-Time Container Tracking
{
Track MSC containers live with vessel name, voyage number, ETA, ATD, and current port. Stay informed and respond instantly to schedule or route changes.
}
Multi-Carrier Container Tracking
{
Manage containers from MSC, Maersk, CMA CGM, ZIM, Hapag-Lloyd, and more. All through one unified API.
}
Easy API Integration
{
Data is provided in JSON format, making it easy to connect JSONCargo’s API with your ERP, TMS, or WMS systems and automatically sync port activity and container events across your tools.
}
Frequently Asked Questions about MSC Tracking API
Get answers to commonly asked questions
The MSC Container Tracking API by JSONCargo allows users to track containers from the MSC shipping line in real time. It provides complete shipment visibility, including container status, location, ETA, vessel details, and port activities—all accessible through a single API connection.
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.
The API provides detailed container arrival data, including real-time shipment status, loading and discharging ports, vessel name, voyage number, ETA, ATD, and Bill of Lading (B/L) tracking details. This information helps businesses manage logistics more efficiently and stay updated throughout the shipping process.
Getting started is simple. Subscribe to the JSONCargo service, complete the payment, and receive your API key. You can then integrate it into your system and begin tracking containers worldwide with instant access to all shipment information.
To track your shipment with JSONCargo, you’ll need either your container number or your Bill of Lading (B/L) number.
- A container number is a unique code printed on the container (e.g., MSCU1234567).
- A B/L number is issued by the shipping line and appears on your shipment documents or booking confirmation.