Migration guides
Migrate from other container tracking services to TimeToCargo API v2
Start with the migration workflow, then choose your provider. Each guide covers request and response differences, examples, and data to retain separately.
Choose your provider
| Current provider | Guide coverage |
|---|---|
| SeaRates | Container Tracking API v3 parameters and responses, plus legacy operations |
| Qubictron | Replacing header authentication, requesting routes and handling errors |
| Navo24 / TrackingMCP | Tracking creation, new IDs, events and notifications |
| ShipsGo | Ocean API v2, stored tracking records, GeoJSON routes and tags |
| GoComet | Bulk reference migration, data retrieval and tracking updates |
| Vizion | Tracking records, updates and document-to-container relationships |
| Terminal49 | Tracking requests, JSON:API, shipments and containers |
| project44 | Ocean tracking in Unified API and Ocean API v4 |
Upgrading from API v1
For an upgrade from TimeToCargo API v1, use the v2 migration guide. It covers changes to parameters, responses and tracking management.
Last updated on