Replace your SeaRates API feed with Dockflow
Container tracking data from 120+ ocean carriers for your platform or TMS. Book a demo to review your integration requirements.
Last updated 6 October 2026.
What happened
SeaRates was discontinued in August 2026 (FreightWaves, 27 August 2026). DP World, which owns the SeaRates business, confirmed to FreightWaves that it no longer operates SeaRates. DP World is also shutting down CARGOES Flow, its shipment-visibility platform. This page is for teams replacing the SeaRates container tracking API.
What to verify for your integration
Compare the fields and event definitions your application needs. Confirm authentication, webhooks or polling, request limits and error handling before agreeing the migration scope. Check data quality against shipment records you already trust.
- Check that carrier coverage includes the long-tail lines, not just the big alliances
- Check that you can look up by bill of lading, booking and container, not container numbers alone
- Check that event data is normalized across carriers, so "gate out" means the same thing whichever line reports it
- Check that both webhooks and polling are available
- Check that ETAs update when a vessel's schedule does
- Check that terminal events for Antwerp and Rotterdam come through, not just carrier milestones
- Check where the data is hosted if any of your customers are in Europe
Dockflow's carrier data
Dockflow, the world's first LogOps platform, covers 120+ ocean carriers, including long-tail lines. The carrier data is available as a data-only offer for platforms, TMS vendors and forwarders that pulled data through the SeaRates API, including at small volumes.
What is included:
- 300+ integrations
- B/L-level tracking alongside booking and container references, so you do not re-key every shipment as a bare container number
- Data quality: GraphTP reconciles carrier and terminal data when two sources disagree
- EU-hosted infrastructure, in line with GDPR
Want more than a feed? Container visibility, Automation and the Customer portal sit on the same data, and predictive visibility goes one step past tracking.
Book a demo to compare your carrier coverage and API requirements with Dockflow.
Migration in 3 steps
- Identify the shipment references and API fields your integration uses.
- Compare Dockflow's responses with your required fields and any saved SeaRates responses.
- Agree who changes the integration and how it will be tested before switching.
Agree the migration schedule after reviewing your carriers and the changes your integration needs.
Proof
Dockflow covers 120+ ocean carriers, including long-tail lines, with B/L-level tracking alongside booking and container references.
Container monitoring at Intercont Freight Liners
“Before Dockflow, we needed 2 full-time employees to continuously monitor our shipments in transit.”
Gaurav Sethi, CEO, Intercont Freight Liners
Last year $21 billion worth of cargo moved through Dockflow, across the supply chains of more than 15,000 companies.
Frequently Asked Questions
Is SeaRates shutting down?
Yes. SeaRates was discontinued in August 2026. DP World confirmed to FreightWaves on 27 August 2026 that it no longer operates the SeaRates business.
What happens to my SeaRates container tracking data?
SeaRates has not published a data export process, and no vendor, Dockflow included, can speak for what happens to your historical data on SeaRates' side. What you control is where your live tracking runs next. Gather the reference list of containers, B/Ls and bookings you hold, so you have it regardless.
Which changes does my integration need?
That depends on how your application uses the SeaRates API. Compare the fields, event definitions, authentication and webhook or polling setup it relies on with Dockflow's. Then agree who changes the integration and how it will be tested before you switch.
How do I migrate from the SeaRates API to another container tracking API?
Identify the shipment references and API fields your integration uses, compare Dockflow's responses with your required fields and any saved SeaRates responses, and agree who changes the integration and how it will be tested before switching.
How long does it take to switch off SeaRates?
It depends on the carriers and systems involved. Agree the migration schedule after reviewing your carriers and the changes your integration needs.
Can I keep my SeaRates container references when I switch?
Yes. Dockflow's migration starts from your existing reference list of container numbers, B/Ls and bookings. You do not rebuild it from scratch.
Which carriers does the replacement cover compared to SeaRates?
Dockflow covers 120+ ocean carriers, including long-tail lines. If a specific carrier mattered to your SeaRates setup, ask Dockflow directly. Coverage is confirmed before you commit to anything.
How can I check event coverage and data quality before switching?
Compare Dockflow's event definitions with the ones your application expects, and test the data against shipment records you already trust. Dockflow goes through the comparison with you in a demo. Field mapping and coverage are confirmed per integration, with no promise of identical output.
Keep your carrier data flowing
Book a demo to compare your carrier coverage and API requirements with Dockflow.
Book a demo