Authentication
All API requests must include your API key as a Bearer token in the Authorization header. You can generate and manage API keys from the Developer section of your dashboard.
Authorization: Bearer sk_live_YOUR_API_KEY
Base URL
All endpoints are relative to the following base URL:
https://traqocontainer.com/api/v1
Errors
All error responses return JSON with a consistent structure:
{
"statusCode": 401,
"statusMessage": "Invalid or missing API key"
}| Status | Meaning |
|---|---|
200 | Success |
400 | Bad request — check required parameters |
401 | Invalid or missing API key |
402 | Shipment limit reached — upgrade your plan |
403 | Developer mode not enabled — enable it from your dashboard settings |
404 | Resource not found |
429 | Rate limit exceeded |
502 | Upstream tracking API error — retry after a moment |
Shipment limits
There are no API call limits. The only constraint is how many shipments your account can track simultaneously — this is your shipment slot limit, set by your plan.
Each call to /api/v1/container/:number, /api/v1/bl/:number checks whether the shipment is already in your account. If it is, the call succeeds without consuming a slot. If it's new and you have remaining slots, it's added. If you've reached your limit, the API returns 402.
Deleting a shipment from your dashboard frees up that slot immediately. Your current usage and slot limit are visible on the Developer tab in your dashboard.
/api/v1/vessel/track and /api/v1/voyage/schedules endpoints do not consume shipment slots — they are purely lookup calls. /api/v1/container/:numberTrack a container
Returns full tracking data for a container number — status, route, ETA, port events, and vessel info. Pass the container number directly in the URL. The shipment is automatically saved to your account in the background.
403.Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
number | string | Yes | Container number (e.g. MSCU1234567) |
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
sealine | string | No | SCAC code of the shipping line (e.g. MSCU) — improves accuracy |
curl -H "Authorization: Bearer sk_live_YOUR_API_KEY" \ "https://traqocontainer.com/api/v1/container/MRSU6859427?sealine=MAEU"
Response
/api/v1/bl/:numberTrack a bill of lading
Returns full tracking data for a Bill of Lading number. Identical response structure to the container endpoint. The shipment is automatically saved to your account in the background.
403.Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
number | string | Yes | Bill of Lading number |
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
sealine | string | No | SCAC code of the shipping line — improves accuracy |
curl -H "Authorization: Bearer sk_live_YOUR_API_KEY" \ "https://traqocontainer.com/api/v1/bl/SHZ8037930?sealine=CMDU"
Response
/api/v1/shipmentsList tracked shipments
Returns a paginated list of all shipments saved to your account — containers and bills of lading — with their current status, route, and ETA. Useful for building dashboards and monitoring multiple shipments at once.
403.Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | No | Page number, default 1 |
pageSize | integer | No | Results per page, default 20, max 100 |
curl -H "Authorization: Bearer sk_live_YOUR_API_KEY" \ "https://traqocontainer.com/api/v1/shipments?page=1&pageSize=20"
Response
Showing 2 of 4 items for brevity. Flat objects — no nested arrays.
/api/v1/vessel/trackTrack a vessel
Returns real-time AIS position, speed, heading, and voyage information for a vessel. Both imo (7 digits) and mmsi (9 digits) are required.
403.Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
imo | string | Yes | 7-digit IMO number |
mmsi | string | Yes | 9-digit MMSI number |
curl -H "Authorization: Bearer sk_live_YOUR_API_KEY" \ "https://traqocontainer.com/api/v1/vessel/track?imo=9811000&mmsi=636022327"
Response
/api/v1/voyage/schedulesVoyage schedules
Returns sailing schedules between two ports for a given date, across available carriers.
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
origin | string | Yes | Origin port UN/LOCODE (e.g. CNSHA) |
destination | string | Yes | Destination port UN/LOCODE (e.g. NLRTM) |
date | string | Yes | Date in YYYY-MM-DD format |
week_range | integer | No | Number of weeks to search, default 1 |
date_type | string | No | "departure" (default) or "arrival" |
curl -H "Authorization: Bearer sk_live_YOUR_API_KEY" \ "https://traqocontainer.com/api/v1/voyage/schedules?origin=INMUN&destination=AEJEA&date=2026-06-01&week_range=2&date_type=departure"
Response
Showing 2 of many results for brevity.