Vizion Container API

Vizion's value proposition is narrowness. It does not try to be your visibility platform; it tries to be the normalization layer underneath one. Roughly 7,000 carrier and terminal event codes collapse into 60 standardized milestones, and you consume them as JSON over a REST API with webhooks firing when a new event lands or a shipment changes. If you have ever maintained a switch statement mapping forty carriers' status codes into your own enum, that is the job Vizion is selling to take off your hands. The input side is better thought through than most. You can subscribe with container number plus carrier code, with master bill of lading, or hand it a container with no carrier and let Automatic Carrier Identification resolve it — the last one matters in practice, because your TMS often does not know the ocean carrier at the moment a booking is created. EDI, AIS, and port/terminal feeds are pre-wired, refreshed multiple times daily, which Vizion states as six hours or less of latency. Coverage spans ocean plus Class I North American intermodal rail, and a single request can follow a box across both legs. Data-quality claims on the homepage: 99.99% uptime, 98% of shipments tracked, 300M+ events processed. The features that justify a contract rather than a spreadsheet are the operational ones. Last Free Date alerts fire before demurrage free time expires — for a drayage team, one avoided detention week pays for a lot of API. Port Performance Monitoring gives arrival-to-berth, time at mooring, and gate-out duration so routing decisions stop being vibes. The 2026 layer is booking pressure. SDPI reads booking volumes 7 to 14 days ahead of rate movement across 16 trade lanes and port pairs. Vizion's own public read had West Coast tightening flagged for weeks before the World Container Index climbed 4% to $4,526 on August 20, 2026. Its June 2026 apparel dataset — 21,434 TEU into the US, the strongest June in 12 years — and the Vietnam-to-US bookings running 19% ahead of 2025 are the kind of specifics you can actually check. TradeView, sold alongside rather than bundled, adds 130+ data sources, a 10-year archive, 625K named companies, and risk intel across about 2B shipments. Weaknesses are real. There is no dashboard to log into on day one — you build the view or embed it in your product. Coverage stops at ocean and Class I North American rail; domestic truckload, air, and parcel are out of scope, so a multimodal shipper still needs a second vendor for the last mile (project44 and FourKites cover more modes but hand you their UI and their opinions). Integration is engineering work: API keys, JSON handling, webhook endpoints, error paths. SDPI covers 16 lanes, not the world. And TradeView and Supply Chain Optimization are separate products, so budget them as add-ons rather than assuming they come with the tracking feed.