ECGridOS is the Web Service API for the ECGrid Interconnect Infrastructure. Every connection, every protocol, every trading partner and transaction, accessible to your application through one coherent API surface, publicly available as an API for 18 years and running on infrastructure ECGrid has operated since 1999.
The teams who build external B2B connectivity into their systems do not build their own networks. They build on ours. ECGridOS is how.
The old model: you bought VAN service, you ran translation software, and your customers lived inside someone else's portal. ECGridOS rewrites the shape of the deal. The infrastructure underneath is the same ECGrid infrastructure that has carried B2B traffic for decades. The surface your team works against is a clean, versioned Web Service API.
Your application calls the API. ECGridOS handles the session, the protocol negotiation, the partner onboarding, the parcel delivery, and the operational telemetry. Your customer never sees us. They see your product.
Move from the architecture view into the full ECGridOS catalog: users, mailboxes, networks, trading partners, certificates, parcels, reporting, and routing.
ECGridOS is organized around real operational concerns your product has to handle. Pick the groups you need for the version of B2B you are shipping. Add the rest later without another integration. Every group is consumable from the same endpoint, with the same session, the same credentials, the same versioning discipline.
Authenticate, manage the user directory, mint and rotate API keys. Every integration starts here with Login and closes with Logout. Built around a stable session model that has been the front door to ECGridOS since its public release in 2009.
Provision the community. Create networks for your customers, add mailboxes, branch out sub-accounts, suspend and terminate as the lifecycle demands. Every community on ECGrid is built and managed through these operations.
Onboard new partners and customers programmatically. Manage ECGridIDs and the X12 or EDIFACT qualifier pairs that route real traffic. Partner setup that used to take weeks now happens in the time it takes to make a few API calls.
Configure AS2 connections, manage private and public certificates, pair comm profiles between trading IDs. Full lifecycle for the protocols and credentials that keep your traffic moving and your compliance surface clean.
The data plane. Upload X12, EDIFACT, Tradacoms, VDA, and MFT payloads. Poll the InBox, download, confirm, archive. Pull per-transaction manifests for evidence, resend on demand. This is where traffic actually moves.
Operational visibility on your terms. Pull traffic statistics at any granularity, look at instant statistics for a session or mailbox, and stream interchange-level reporting into your own dashboards. The live system graph on ECGridOS.net is powered by one of these public reporting operations.
Network federation and secondary routing. Manage formal Interconnect requests between ECGrid and partner networks, and configure carbon copy rules so every party on a transaction receives an auditable copy.
200+ operations across every capability group, each with signature and parameter documentation. Versioned, stable, and production-hardened since version 1.
A trading partner publishes an 856. Your application needs to receive it, persist it, and confirm the download. Login, poll, download, confirm, logout. This is the shape of every ECGridOS receive integration.
// Receive all waiting parcels for a mailbox const session = await ecgridos.Login({ LoginName: USER, Password: PASS }); const { Parcels } = await ecgridos.ParcelInBox({ SessionID: session.SessionID }); for (const p of Parcels) { const { Payload } = await ecgridos.ParcelDownload({ SessionID: session.SessionID, ParcelID: p.ParcelID }); await myApp.persist(Payload); await ecgridos.ParcelDownloadConfirm({ SessionID: session.SessionID, ParcelID: p.ParcelID }); } await ecgridos.Logout({ SessionID: session.SessionID });
{
"Parcels": [
{
"ParcelID": 4918322,
"MailboxID": 102847,
"Sender": "WALMART",
"Qualifier": "ZZ",
"DocumentType": "856",
"ControlNumber": "000000142",
"MailbagControlID": "0000000142",
"Size": 8421,
"Received": "2026-04-17T09:12:44Z",
"Status": "Available"
},
{
"ParcelID": 4918323,
"MailboxID": 102847,
"Sender": "TARGET",
"Qualifier": "ZZ",
"DocumentType": "850",
"ControlNumber": "000000876",
"MailbagControlID": "0000000876",
"Size": 12384,
"Received": "2026-04-17T09:12:51Z",
"Status": "Available"
}
]
}
Two tiers to get you building. Demo is the evaluation environment with the full API surface and sandbox mailboxes, no card on file. Developer is the paid tier that opens live VAN and trading partner traffic. For production volume and commercial terms, talk to our team.
For teams evaluating the platform. Self-contained environment, no time limit, no card on file.
Production infrastructure for active integration work. Live VAN connections and real trading partner traffic.
Start with the full program details, or go straight into the developer portal if your team is ready to provision.