Stedi Raises $50M Series C for API-First EDI
Stedi closed a $50M Series C for API-native EDI. See what this funding signals for supply chain teams evaluating API-first B2B integration.
Stedi closed a $50 million Series C on March 30, 2026, led by Addition, with participation from Stripe, Ribbit Capital, USV, First Round, BoxGroup, and Bloomberg Beta, plus angel investors including Shopify's Tobi Lütke, according to Stedi's own announcement and confirmed by FinSMEs. The round pushes Stedi's total funding to $142 million. If you run EDI for a manufacturer, retailer, or 3PL, this is worth five minutes of your attention, and not because Stedi sells to your industry directly right now.
What Stedi actually raised money to build
The round is framed around healthcare: eligibility checks, claims, and remittance processing for a network Stedi says now covers more than 3,400 U.S. payers. But the underlying architecture is the same one Stedi originally built for general B2B EDI. Founder Zack Kanter has been explicit about this lineage: HIPAA mandated the X12 EDI standard for healthcare transactions, "the very same transaction standard used in the retail, logistics, and manufacturing industries that run the global supply chain." Kanter's own background isn't healthcare. He previously ran a B2B auto parts transaction platform before founding Stedi, and used X12 EDI extensively in integrations with automotive retailers that distributed his products. Healthcare is where the money is right now. Supply chain EDI is where the pattern started.
The pitch investors bought: EDI without the VAN tax
Stedi's core complaint about incumbent clearinghouses and VANs is one every EDI manager will recognize instantly. In its funding announcement, Stedi describes legacy systems that don't offer APIs outside basic functionality, actively block bots from using their web portals, and charge exorbitant fees to remove those restrictions, leaving customers stuck in a cat-and-mouse game with breaking portal changes that quietly stop working. Swap "claims portal" for "VAN mailbox" and this is the exact frustration EDI teams have with SFTP pickup windows, batch cycles, and integrator-gated API access.
The growth numbers back up investor confidence in the model. Stedi's paying customer base grew 6x year over year, with billed transactions increasing over 7x, and the platform now processes more than a billion claims and eligibility transactions annually. That's not a pilot-stage curiosity. That's a company operating at production scale on a JSON-native, API-first model that treats X12 as an input format to translate, not a wire protocol you build your integration around.
Why this isn't only a healthcare story
Stedi's roots as an EDI platform for automating B2B transactions go beyond claims processing. According to Tracxn's company profile, the platform supports integrations with ERP systems and webstores including Flexport, Amazon, Walmart, Costco, and NetSuite, letting customers trade EDI-compliant purchase orders, invoices, and advance ship notices. That's retail and logistics EDI, not medical claims. The "translate X12/EDIFACT into JSON, expose it via API" pattern investors just backed at $142 million in cumulative funding is the identical pitch Orderful and Crstl have been making to supply chain teams for the past few years.
What this signals if you manage trading partner EDI
A company this well-funded betting its future on API-first EDI is a market signal, not just a healthcare headline. Expect incumbents like SPS Commerce, TrueCommerce, Cleo, IBM Sterling, and OpenText to accelerate their own API layers rather than lose developer mindshare to newer entrants. You're already seeing the same abstraction happen one layer over in transport. Shippers running multi-carrier operations expect TMS and carrier connectivity platforms like MercuryGate, Descartes, Blue Yonder, and Uber Freight to hide EDI/API differences behind a single connection. Tools built specifically for that abstraction, such as Cargoson, ShippyPro, Sendcloud, and EasyPost, are racing to make carrier connectivity format-agnostic. Trading-partner EDI is heading the same direction, just a few years behind.
| Milestone | Detail |
|---|---|
| Series C close | March 30, 2026 |
| Series C amount | $50 million |
| Total funding to date | $142 million |
| Lead investor | Addition |
| YoY customer growth | 6x |
| YoY transaction volume growth | 7x |
What to actually do about it
Don't plan a rip-and-replace of your VAN infrastructure off the back of one funding round. Do use it as leverage and a planning input over the next two quarters.
- Audit your top 20 trading partners' EDI compliance documents for JSON or REST alternatives some already offer through provider partners, even if buried below the primary X12 spec.
- Ask your current VAN or EDI provider directly for their API roadmap and a committed timeline, not a slide deck promise.
- For new partner onboarding over the next 6 to 12 months, build a hybrid bridge: keep X12 in on the wire, but normalize to JSON internally so future partners who do offer APIs don't require a separate integration pattern.
- Watch whether your incumbent's next release notes mention agentic workflows or bot access restrictions loosening. That's the tell that they're responding to competitive pressure like Stedi's.
Bottom line
One funding round doesn't mandate anything. But $142 million in cumulative venture capital riding on a JSON-native, API-first EDI architecture is the clearest recent proof point that this model is investable at scale, not a niche developer preference. That changes the leverage you have in your next contract renewal conversation with your VAN or EDI provider, whether or not you ever touch a Stedi product yourself.
