Container Tracking API

The Container Tracking API is a software tool that enables users to retrieve real-time information about the whereabouts and status of shipping containers. This API provides data on the location, temperature, and other parameters of the container, making it useful for logistics companies, retailers, and manufacturers who need to track their goods as they move through the supply chain. With this API, users can optimize their operations and provide better customer service by proactively managing container logistics.

About the API: 

The Container Tracking API is a powerful tool that allows companies to track and monitor their shipping containers in real-time. This API enables users to retrieve a wealth of information about the container, such as its current location, temperature, and other important parameters. This data can be used to optimize logistics operations, improve supply chain efficiency, and provide better customer service.

The Container Tracking API can be integrated into a wide range of systems and applications, making it highly flexible and adaptable to different use cases. For example, logistics companies can use this API to provide their customers with real-time updates on the location and status of their shipments, reducing the need for manual tracking and improving transparency.

Manufacturers can also benefit from the Container Tracking API by monitoring the movement of their products through the supply chain. By tracking containers and their contents, manufacturers can optimize production schedules, reduce waste, and improve inventory management. They can also use the data from the API to identify potential issues or delays in the supply chain, enabling them to take corrective action before it becomes a problem.

Retailers can also use the Container Tracking API to improve their supply chain operations. By tracking the movement of shipping containers containing their products, retailers can ensure that they have the right inventory in stock at the right time. This can help them avoid stockouts and reduce the need for costly expedited shipping.

In addition to its tracking capabilities, the Container Tracking API also provides a range of analytics tools that enable users to analyze the data collected by the API. This includes tools for visualizing container movement patterns, identifying bottlenecks in the supply chain, and tracking key performance indicators (KPIs) such as on-time delivery rates and inventory turnover.

Overall, the Container Tracking API is a valuable tool for companies operating in the logistics and supply chain industries. By providing real-time tracking and monitoring of shipping containers, this API enables companies to optimize their operations, reduce costs, and provide better customer service.

 

What this API receives and what your API provides (input/output)?

Pass any MBL code and receive the relevant information from the container. 

  

What are the most common uses cases of this API?

There are several use cases for the Container Tracking API, including:

  1. Logistics and freight companies can use the API to track their shipments and provide real-time updates to customers. This can help improve customer satisfaction and reduce customer inquiries related to shipment status.

  2. Manufacturers can use the API to monitor the movement of their products through the supply chain, ensuring that they are delivered on time and in the correct condition. This can help reduce waste, optimize production schedules, and improve inventory management.

  3. Retailers can use the API to track the movement of their products from the manufacturer to the store, helping to ensure that they have the right inventory in stock at the right time. This can help reduce stockouts and improve customer satisfaction.

  4. Shipping companies can use the API to optimize their operations, such as by identifying inefficiencies in their supply chain and optimizing delivery routes to reduce fuel costs.

  5. Government agencies can use the API to monitor the movement of hazardous materials or other regulated substances, ensuring that they are being transported safely and in compliance with regulations.

  6. Insurance companies can use the API to monitor the location and condition of insured cargo, reducing the risk of losses and improving underwriting accuracy.

  7. Third-party logistics providers (3PLs) can use the API to track the movement of multiple shipments for multiple clients, providing a consolidated view of their operations and helping to optimize their overall logistics network.

In summary, the Container Tracking API is a versatile tool that can be used in a variety of industries and applications to improve supply chain visibility, optimize logistics operations, and provide better customer service.

 

Are there any limitations to your plans?

Besides the number of API calls, there is no other limitation

API Documentation

Endpoints


This endpoint will generate a JOB request for your query. Later you will be able to retrieve the response with that JOB ID. 

Pass the MBL code or container code to this endpoint, and also the Shipping Line code. 

 

Supported Shipping Line codes:

  • ACL
  • ADMIRAL LINE
  • AKKON LINES
  • ANL
  • APL
  • ARKAS LINE
  • AVANA LOGISTEK ( BALAJI )
  • BAHRI LINE
  • BAL LINE
  • BLPL SINGAPORE
  • BLUE WATER LINES
  • BMC LINES
  • CK LINE
  • CMA CGM
  • CNC LINE
  • CONTAINERSHIPS (CONTAZ)
  • CORDELIA SHIPPING LINE
  • COSCO
  • COSIARMA
  • CU LINES
  • DAL
  • DONG YOUNG SHIPPING
  • DONGJIN SHIPPING
  • ECON SHIPPING
  • ECU WORLDWIDE
  • EMIRATES LINE
  • EMKAY LINE
  • EVERGREEN
  • FESCO
  • GOLD STAR LINE
  • GRIMALDI
  • HAFEZ DARYA (HDASCO)
  • HAMBURG SUD
  • HAPAG LLOYD
  • HEUNG A
  • HYUNDAI MM
  • INDUS C LINES
  • INTERASIA
  • K LINE (RO-RO)
  • KAMBARA KISEN
  • KMTC
  • LESCHACO
  • MACS
  • MAERSK LINE
  • MARFRET LINES
  • MARGUISA
  • MARIANA EXPRESS LINES (MELL)
  • MATSON
  • MAXICON
  • MEDKON
  • MELFI MARINE
  • MESSINA LINE
  • MILAHA
  • MSC
  • NAMSUNG SHIPPING
  • NATIONAL SHIPPING OF AMERICA
  • NILE DUTCH
  • NIRINT SHIPPING
  • ONE LINE
  • OOCL
  • OTHERS
  • PAN ASIA
  • PAN OCEAN
  • PASHA HAWAII
  • PIL
  • PSL NAVEGACAO
  • RCL
  • SAMUDERA
  • SARJAK CONTAINER LINE
  • SASCO
  • SAVANA LINE
  • SCI
  • SEA LEAD SHIPPING
  • SEALAND
  • SHAL ASIA
  • SIDRA LINE
  • SINOKOR
  • SINOTRANS
  • SITC LINE
  • SM LINE
  • SPIL
  • STOLT TANK CONTAINERS
  • SUNMARINE LINE
  • SWIRE SHIPPING
  • TARROS
  • TOTE MARITIME
  • TRANS ASIA LINE
  • TRANSFAR SHIPPING
  • TRANSVISION SHIPPING
  • TROY CONTAINER LINE
  • TS LINES
  • TURKON LINE
  • VOLTA SHIPPING
  • WALLENIUS LINES
  • WAN HAI LINES
  • WEC LINES
  • YANG MING


                                                                            
POST https://zylalabs.com/api/1751/container+tracking+api/1367/create+request
                                                                            
                                                                        

Create Request - Endpoint Features

Object Description
blContainersRef [Required] The MBL code of reference.
shippingLine [Required] The shipping line code. EX: HAPAG LLOYD
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            4249968
                                                                                                                                                                                                                    
                                                                                                    

Create Request - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/1751/container+tracking+api/1367/create+request?blContainersRef=Required&shippingLine=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

This endpoint will retrieve the response with the JOB ID generated in the Create Request endpoint. 



                                                                            
GET https://zylalabs.com/api/1751/container+tracking+api/1368/retrieve+response
                                                                            
                                                                        

Retrieve Response - Endpoint Features

Object Description
requestId [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            [
    {
        "Message": "Success",
        "Status": "Discharged",
        "StatusId": 50,
        "ReferenceNo": "",
        "BLReferenceNo": "HLCUBU3220827900",
        "ShippingLine": "HAPAG LLOYD",
        "ContainerNumber": "TCNU1051902",
        "ContainerTEU": "40",
        "FromCountry": "CHINA",
        "Pol": "SHANGHAI",
        "LoadingDate": {
            "Date": "2022-10-23",
            "IsActual": true
        },
        "DepartureDate": {
            "Date": "2022-10-23",
            "IsActual": true
        },
        "TSPorts": [
            {
                "Port": "BUSAN (PUSAN)",
                "ArrivalDate": {
                    "Date": "2022-10-25",
                    "IsActual": true
                },
                "DepartureDate": {
                    "Date": "2022-10-31",
                    "IsActual": true
                },
                "Vessel": "YM WELLBEING",
                "VesselIMO": "9820908",
                "VesselLatitude": "Not Supported",
                "VesselLongitude": "Not Supported"
            },
            {
                "Port": "JEBEL ALI",
                "ArrivalDate": {
                    "Date": "2022-11-24",
                    "IsActual": true
                },
                "DepartureDate": {
                    "Date": "2022-12-04",
                    "IsActual": true
                },
                "Vessel": "NORTHERN DEXTERITY",
                "VesselIMO": "9345996",
                "VesselLatitude": "Not Supported",
                "VesselLongitude": "Not Supported"
            }
        ],
        "ToCountry": "KUWAIT",
        "Pod": "SHUAIBA",
        "ArrivalDate": {
            "Date": "2022-12-06",
            "IsActual": true
        },
        "DischargeDate": {
            "Date": "2022-12-06",
            "IsActual": true
        },
        "Vessel": "ATHOS",
        "VesselIMO": "9406738",
        "VesselLatitude": "Not Supported",
        "VesselLongitude": "Not Supported",
        "GateOutDate": "2023-01-03",
        "EmptyReturnDate": "2023-01-03",
        "FormatedTransitTime": "44 days",
        "ETA": "-",
        "FirstETA": "2022-12-06",
        "BLContainerCount": 4,
        "BLContainers": [
            {
                "ContainerCode": "DFSU6483194",
                "ContainerTEU": "40",
                "LiveMapUrl": "https://shipsgo.com/live-map-container-tracking?query=DFSU6483194",
                "BLGateOutDate": "2023-01-03",
                "BLEmptyReturnDate": "2023-01-03"
            },
            {
                "ContainerCode": "FSCU8946539",
                "ContainerTEU": "40",
                "LiveMapUrl": "https://shipsgo.com/live-map-container-tracking?query=FSCU8946539",
                "BLGateOutDate": "2023-01-03",
                "BLEmptyReturnDate": "2023-01-03"
            },
            {
                "ContainerCode": "UACU5648077",
                "ContainerTEU": "40",
                "LiveMapUrl": "https://shipsgo.com/live-map-container-tracking?query=UACU5648077",
                "BLGateOutDate": "2023-01-03",
                "BLEmptyReturnDate": "2023-01-03"
            }
        ],
        "LiveMapUrl": "https://shipsgo.com/live-map-container-tracking?query=TCNU1051902",
        "Tags": []
    }
]
                                                                                                                                                                                                                    
                                                                                                    

Retrieve Response - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/1751/container+tracking+api/1368/retrieve+response?requestId=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Container Tracking API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
100%
 Response Time
370ms

Category:


Related APIs