Building the modern
Peppol sending platform.
Peppol is the backbone of B2B e-invoicing across 40+ countries, yet sending a single invoice still requires enterprise contracts and XML-era toolchains. It doesn't have to be that way. We want to change that.
Why a developer-first Peppol API needs to exist
Belgium mandates Peppol e-invoicing from 2026. France, Germany, Spain, and Poland are next. Within five years, every company selling to another company in the EU will need to send machine-readable invoices over a regulated network.
Yet the ecosystem is locked behind enterprise sales calls, opaque pricing, and XML toolchains designed in 2008. Want to send a single invoice? Sign a contract. Wait for onboarding. Parse WSDL. Wrap your payload in an ASiC-E container, stuff it inside an SBDH envelope, validate it against Schematron rules nobody has memorised, and pray the receiving access point doesn't bounce it with an undocumented error code.
No startup, indie developer, or AI agent should need a six-month procurement cycle and a five-figure contract to send a single invoice.
As we started to dig deeper, it became clear that the problem wasn't just bad tooling — it was that nobody was building for developers. AI agents and modern SaaS products need to send and receive compliant invoices programmatically — JSON in, valid UBL out, delivered over Peppol — without wrestling with the plumbing.
So we started building peppol.sh: one POST to /v1/invoices, one webhook when it's delivered. That's the surface area. The compliance, validation, network routing, and document packaging stay behind the API where they belong. We're creating something special here, and we're excited to build it with you.
What we believe
The API is the product
If your API needs a dashboard to be useful, the API isn’t finished. Every peppol.sh workflow — signup, KYC, sending, tracking — works from a terminal or an AI agent. The dashboard is a convenience, not a crutch.
Pricing is on the website
“Contact sales for pricing” is a filter for enterprise budgets, not a business model. We publish our per-document rate on the website. You know the cost before you write a line of code.
Compliance is our job, not yours
EN 16931 validation, Peppol BIS 3.0 conformance, SBDH envelopes, SMP lookups, AS4 transport — you shouldn’t have to know what any of that means. Send JSON. We handle the rest.
Sandbox from second zero
You should be able to send a test invoice within sixty seconds of hearing about us. No credit card, no approval queue, no NDA. Sandbox keys are instant and free forever.
AI agents are first-class users
Our API is designed so an AI agent can discover endpoints, authenticate, and send invoices without human intervention. Machine-readable docs, predictable error codes, and structured responses mean autonomous software can integrate peppol.sh the same way a developer would.
Where peppol.sh sits in the Peppol ecosystem
The market has four tiers. We built peppol.sh because Tier 1 barely existed — and no one in it was optimising for developer experience.
Transparent developer-self-serve APIour tier
Public pricing, instant signup, OpenAPI spec, typed SDKs, webhooks, observability. You read the docs, you ship the integration, you pay per document. No sales call required.
Recommand is the nearest domestic competitor (€29/200 docs, €99/1K docs). peppol.sh competes on DX, not price — OpenAPI spec, typed SDKs, webhooks, observability, Cloudflare edge delivery.
End-user accounting SaaS with Peppol bundled
Peppol send is effectively free but locked inside their UI. Not embeddable, not composable. You can’t call their Peppol from your product.
peppol.sh wins by being the only way to embed Peppol into a third-party product.
Premium API infrastructure, opaque pricing
Capable APIs, but you’ll need a sales conversation, a monthly minimum, and patience.
peppol.sh’s wedge: no monthly minimum, transparent per-unit pricing, premium DX, Belgian-domiciled under BPA’s lighter regulatory touch.
Legacy enterprise EDI / Peppol
Five-to-six-figure annual contracts, multi-month procurement cycles, XML-era toolchains. This is what you’re not.
Ready to send your first Peppol invoice?
One curl to sign up. One curl to send. No UI, no approval, no credit card.
Start for free →