CargoWise is powerful, but its eAdaptor interface — and the Universal and Native XML that flow through it — was built for systems integrators, not for a quick connection between two modern apps. Chain.io sits in the middle: you call straightforward APIs, and the platform handles the XML, the connectivity, and the security so your project ships on time.
Skip the Universal XML learning curve. Call modern APIs and let Chain.io handle the CargoWise eAdaptor connection.
CargoWise API Documentation: eAdaptor & Universal XML Integration
Looking for CargoWise API documentation? CargoWise connects through eAdaptor and Universal XML, not a simple REST API. Chain.io lets you call modern APIs and converts them to CargoWise XML for you — connectivity, certificates, and security included.
Speak modern, deliver CargoWise.
eAdaptor and eAdaptor Next, handled.
One trusted connection, many scoped APIs.
Connect once, scale everywhere.
Your developers shouldn't have to learn CargoWise XML.
Connecting to CargoWise: eAdaptor, Universal XML, and how Chain.io makes it easy
If you’re looking for CargoWise API documentation, you’re usually trying to answer one practical question: how do I get data in and out of CargoWise and connected to another system? The detailed technical specs live behind WiseTech’s CargoWise platform and partner program, so we can’t republish them here. What we can do is give you a clear, plain-English overview of how CargoWise connectivity actually works — and show you how Chain.io removes most of the hard parts.
What is CargoWise eAdaptor (and eAdaptor Next)?
eAdaptor is how CargoWise talks to the outside world. Rather than a typical REST API with simple JSON endpoints, it’s a message-based interface: external systems exchange structured XML documents with your CargoWise environment. eAdaptor Next is WiseTech’s modern evolution of that gateway, adding OAuth2, JSON Web Tokens (JWTs), and certificate-based identity and encryption for enterprise-grade security. It’s the long-term direction — and meaningfully harder to stand up. We cover that transition in depth on our CargoWise eAdaptor Next integration page.
eAdaptor moves data in two XML dialects: Universal XML — WiseTech’s standardized, cross-document schema (Universal Shipment, Universal Event, and related types) — and Native XML, CargoWise’s lower-level internal format for working directly with specific entities. Both are powerful, and both were built for integration specialists, not for a quick connection between two modern apps.
What the CargoWise XML interface covers
The Universal and Native XML schemas reach across nearly every CargoWise product area, which is part of why they’re so large. That includes:
- Operational documents — Shipments, Bookings, Quick Bookings, Consolidations, Transport Orders, and more
- Master data — Products, Customers, and other Organizations
- Accounting — the full range of financial and accounting data
Mapping your application’s data into the correct structure — with the right qualifiers, codes, and nesting — is where most CargoWise integration projects lose weeks of engineering time.
A word on security: eAdaptor access is all-or-nothing
This is the part most teams underestimate. A system connected directly to eAdaptor is, by design, fully trusted — it can reach all of your CargoWise data, across every product area above. There’s no built-in way to hand one trading partner a narrow, read-only slice. That makes security the single most important consideration in any CargoWise integration, and it’s why an enterprise-grade middleware layer between eAdaptor and the outside world isn’t a nice-to-have — it’s essential.
The challenge with connecting directly
Building a direct CargoWise integration in-house usually means your team has to:
- Learn the Universal and Native XML schemas and map every field correctly in both directions
- Stand up and maintain eAdaptor connectivity, including endpoints and retries
- Implement authentication — and, for eAdaptor Next, manage certificates, JWTs, and OAuth2 token exchange
- Monitor for failures, certificate expirations, and message rejections
- Carefully control what each downstream system can see — since eAdaptor itself won’t scope it for you
- Repeat much of this work for every new trading partner or system
That’s real software development, infrastructure, and ongoing security work — before you move a single shipment.
How Chain.io makes CargoWise integration easy
Chain.io is an integration platform purpose-built for the supply chain. You connect one trusted endpoint to eAdaptor, the platform secures that connection — certificates, JWTs, OAuth2, and token rotation included — and then you expose clean, well-scoped developer APIs on top of it using the Chain.io Standard JSON formats documented at docs.chain.io. Instead of writing CargoWise XML, your team (and your customers) work with modern REST and JSON.
Here’s what that gives you:
- Scoped APIs, not full access. Use the platform to mint a unique, narrowly-scoped API endpoint for each customer integration or external system — each one sees only the data it should, even though they all run through a single trusted eAdaptor connection.
- Translation. Your data is mapped into and out of Universal and Native XML through Chain.io’s supply-chain-native data model and Standard JSON formats.
- Connectivity. The platform maintains eAdaptor and eAdaptor Next connections, certificates, JWTs, OAuth2 flows, and token rotation.
- Reliability. Chain.io monitors message flow and alerts on issues so problems get caught before they reach your customers.
- Reuse. That one CargoWise connection powers every integration you build on top of it.
The result: connect through a modern API, and your CargoWise integration goes live in days instead of months — with the security and reliability your customers expect.
Frequently asked questions
Does CargoWise have a REST API?
CargoWise’s primary integration interface is eAdaptor, which exchanges Universal and Native XML messages rather than simple REST/JSON endpoints. With Chain.io, you call a modern API in our Standard JSON format and the platform converts it to the XML CargoWise expects.
Can I get the official CargoWise API documentation here?
No — the detailed eAdaptor, Universal XML, and Native XML specifications are maintained by WiseTech for CargoWise customers and partners. Chain.io provides the connectivity and translation layer so you don’t need to work from the raw schema.
What’s the difference between eAdaptor and eAdaptor Next?
Legacy eAdaptor uses basic authentication. eAdaptor Next adds OAuth2, JWTs, and certificates for stronger security. Chain.io supports both. See our eAdaptor Next page for details.
Is a CargoWise eAdaptor connection safe to expose to partners?
Not directly — any system with eAdaptor access can reach all of your CargoWise data. Chain.io sits in front of eAdaptor so each partner or app gets only a scoped slice through its own API.
How long does a CargoWise integration take?
Because the hard parts are pre-built, customers typically go live in days or weeks rather than the months a from-scratch build requires.
Chain.io connects the systems that move your freight.
When you need to integrate with CargoWise, the platform handles the XML, the connectivity, and the security — so your team can stay focused on running the business.
