Peppol API comparison · 2026-06-23
Best Peppol API in 2026
The best Peppol API depends on what you're building. Below is a fair, up-to-date comparison of the five providers developers actually evaluate — by SDKs, pricing, self-serve onboarding, and how well each handles multi-tenant SaaS.
Short answer
If your SaaS sends e-invoices on behalf of many customers, you want a native multi-tenant model — one API key, N legal entities underneath it, each with its own Peppol identity. getpeppr is built for exactly that. Depending on your priorities, Storecove, e-invoice.be, and peppol.sh are the other serious API-first options — and Basware covers the enterprise end. All compared fairly below.
Peppol API providers, side by side
| Provider | Built for | SDKs | Pricing | Self-serve | Market focus | First invoice |
|---|---|---|---|---|---|---|
| getpeppr Best for SaaS | SaaS platforms embedding Peppol (multi-tenant) | TypeScript + CLI | From EUR 49/mo + usage (dedicated Platform plans) | Yes (sandbox → production) | Belgium live, EU expanding | ~5 min |
| peppol.sh | Developers & AI agents | REST/OpenAPI + TS examples (Python/PHP soon) | Pay-per-doc EUR 0.20→0.10, no monthly (Connect from EUR 250) | Yes (API-first) | EU (Belgium-based) | ~30 sec |
| e-invoice.be | Developers | 5 languages (TS, Python, PHP, Ruby, Java) + MCP | EUR 0.25/invoice (from EUR 350); Enterprise EUR 0.18 | Yes | Belgium-focused (certified BE AP) | < 1 hour |
| Storecove | ERP integrators & platforms | None (OpenAPI spec) | Contact sales | Sales-gated | 31 countries / 30+ networks | Hours–days |
| Basware | Enterprise | None (REST + XML) | Contact sales (enterprise) | No (gated test access) | Global network | Days–weeks |
- Built for:
- SaaS platforms embedding Peppol (multi-tenant)
- SDKs:
- TypeScript + CLI
- Pricing:
- From EUR 49/mo + usage (dedicated Platform plans)
- Self-serve:
- Yes (sandbox → production)
- Market focus:
- Belgium live, EU expanding
- First invoice:
- ~5 min
- Built for:
- Developers & AI agents
- SDKs:
- REST/OpenAPI + TS examples (Python/PHP soon)
- Pricing:
- Pay-per-doc EUR 0.20→0.10, no monthly (Connect from EUR 250)
- Self-serve:
- Yes (API-first)
- Market focus:
- EU (Belgium-based)
- First invoice:
- ~30 sec
- Built for:
- Developers
- SDKs:
- 5 languages (TS, Python, PHP, Ruby, Java) + MCP
- Pricing:
- EUR 0.25/invoice (from EUR 350); Enterprise EUR 0.18
- Self-serve:
- Yes
- Market focus:
- Belgium-focused (certified BE AP)
- First invoice:
- < 1 hour
- Built for:
- ERP integrators & platforms
- SDKs:
- None (OpenAPI spec)
- Pricing:
- Contact sales
- Self-serve:
- Sales-gated
- Market focus:
- 31 countries / 30+ networks
- First invoice:
- Hours–days
- Built for:
- Enterprise
- SDKs:
- None (REST + XML)
- Pricing:
- Contact sales (enterprise)
- Self-serve:
- No (gated test access)
- Market focus:
- Global network
- First invoice:
- Days–weeks
All providers deliver across the full Peppol network — "Market focus" reflects each provider's certification, local-mandate coverage, and positioning, not where it can reach. Competitor details verified against public sources on 2026-06-23; check each provider's site before deciding.
Why "multi-tenant" changes the question
A normal Peppol integration assumes one company sending its own invoices. A SaaS platform is different: each customer is a separate legal entity on the network. These are the criteria that actually matter.
Tenant model
One company sending its own invoices is easy. A SaaS platform needs one integration with N legal entities underneath it — each customer is a separate Peppol participant — not one account per customer.
Programmatic onboarding
Can you register a tenant and mint its per-tenant credentials via API, or does every new customer need a manual setup or a sales call?
JSON in, no XML
You send your data shape; UBL / Peppol BIS Billing 3.0 is generated, validated, and transmitted for you. No XML schemas in your codebase.
Try before you buy
Can you evaluate without a signup wall or a demo call? Offline validation and instant sandboxes shorten the path from curiosity to first invoice.
Certified Access Point backing
A certified Peppol Access Point underneath means compliance, network routing, and certificate management are someone else's job.
Mandate roadmap & pricing model
A new country mandate should be the same code path, not a re-architecture — and pricing should stay predictable as you add tenants and volume.
The providers, fairly
No single provider wins on every axis. Here's where each one is strongest — facts verified on 2026-06-23.
getpeppr
A TypeScript-first Peppol SDK built specifically for SaaS platforms. Multi-tenant from day one: one master API key, N legal entities, per-tenant authorisation built in. You send JSON; UBL / Peppol BIS Billing 3.0 is generated, validated, transmitted, and delivery status comes back via webhooks — no XML in your codebase. You can validate and convert invoices offline first with the CLI (no account, no API key) and sign up only when you're ready to send. It runs on a Storecove certified Peppol Access Point, adds registry-based identity verification (Companies House, VIES, Bolagsverket) for the legal entities you onboard, and when a new EU mandate lands it ships the country-specific layer while your JSON contract stays identical.
Storecove
A certified Peppol Access Point with a RESTful API and connectivity across 31 countries and 30+ e-invoicing networks. It's the infrastructure layer many products build on — getpeppr included. It's a great network, built for ERP integrators and platform vendors rather than self-service developer experience: there are no native language SDKs (you work from the OpenAPI spec), pricing is contact-sales, and production onboarding goes through their team. Choose it if you want direct Access Point access with broad coverage and you're happy to build your own developer experience and tenant model on top.
e-invoice.be
A certified Belgian Access Point with a pay-per-invoice model, no setup fees, and idiomatic SDKs in five languages (TypeScript, Python, PHP, Ruby, Java) plus an MCP server for AI agents. It markets itself as multi-tenant friendly with cost distributed across your customer base. A strong pick when low pay-per-use cost and a wide choice of SDK languages are the priority.
peppol.sh
A developer-centric API: send a JSON payload, it converts to Peppol BIS 3.0 UBL, validates, and delivers. Its embedded model is "one company per tenant, same API" with no per-tenant fees and no monthly subscription — its Connect tier unlocks from a EUR 250 minimum top-up — and you can go live entirely from the terminal or an AI agent. It advertises a typed TypeScript SDK with code examples, though the published npm package wasn't resolvable at the time of writing, and Python and PHP are marked coming soon. A good fit for lean teams and agent-driven workflows.
Basware
Enterprise-grade AP automation and one of the largest e-invoicing networks, certified for Peppol. Integration is via REST APIs and XML rather than native language SDKs, test access is gated through their team, and pricing is enterprise/contact-sales. Best suited to large organisations with very high invoice volumes rather than developer-first SaaS embedding.
Which should you choose?
Match the provider to your situation.
Why getpeppr for multi-tenant SaaS
getpeppr is the best choice for SaaS and ERP platforms that embed Peppol for their customers — not because it wins on price, but because it's built for the platform shape.
- Native multi-tenant. One master API key, N legal entities, per-tenant authorisation built in — not one account per customer.
- Identity verification (Trust Layer). Legal entities you onboard are checked against business registries (Companies House, VIES, Bolagsverket) before they can send.
- TypeScript SDK + CLI. Full type safety, and offline validation from the terminal with no account required — try before you sign up.
- Predictable pricing. A subscription with usage, plus dedicated Platform plans that scale by legal entity — instead of unpredictable per-document costs as you grow.
- Certified Access Point underneath. Runs on a Storecove certified Peppol Access Point, so compliance and network routing are handled. New EU mandate? The country layer ships while your JSON contract stays identical.
Frequently asked questions
What is the best Peppol API for a multi-tenant SaaS?
For SaaS platforms sending invoices on behalf of many customers, the deciding factor is a native multi-tenant model — one API key, many legal entities, with per-tenant onboarding via API. getpeppr is purpose-built for that case; peppol.sh and e-invoice.be also support multi-tenant setups, and Storecove provides the underlying Access Point infrastructure.
Do I have to deal with UBL or XML myself?
No. With API-first providers like getpeppr, peppol.sh, and e-invoice.be you send JSON (or your own data shape) and the provider generates, validates, and transmits the Peppol BIS Billing 3.0 UBL for you.
Can I try a Peppol API before signing up or talking to sales?
Yes. getpeppr offers offline CLI validation with no signup; Storecove and e-invoice.be offer sandboxes; peppol.sh lets you send test invoices from the terminal. Enterprise platforms like Basware typically gate test access behind their sales team.
Which countries does the EU e-invoicing mandate cover, and when?
Belgium mandated B2B e-invoicing from 1 January 2026. Germany has phased requirements underway. France begins its rollout from 1 September 2026. The EU's ViDA package extends digital reporting requirements for cross-border B2B by 1 July 2030. A good Peppol provider absorbs each new mandate without changing your integration.
What does "multi-tenant" mean for Peppol e-invoicing?
Each of your customers is a separate participant on the Peppol network with its own identity. A multi-tenant Peppol API lets your platform register and send for all of them through a single integration, instead of standing up a separate account per customer.
Ready to ship Peppol invoices?
Send your first invoice in 5 minutes. Free sandbox, no credit card, full SDK access.
$ npm install @getpeppr/sdk Free sandbox forever. No credit card required. Ship invoices in minutes.