Peppol API comparison · 2026-06-24

getpeppr vs peppol.sh

Both are developer-first Peppol APIs — JSON in, compliant UBL out, delivered over a certified Access Point. They're built for different buyers. Here's an honest, up-to-date comparison.

Short answer

Choose peppol.sh if you're a solo developer or a low-volume / agent-first builder who wants pay-per-document pricing with no monthly fee. Choose getpeppr if you're a SaaS platform embedding Peppol for many customers — native multi-tenant, registry identity verification, a published SDK + CLI, a dashboard, and predictable pricing as you scale.

Start building freeSee all 5 providers

Head to head

Built for

getpeppr
SaaS platforms embedding Peppol (multi-tenant)
peppol.sh
Solo devs, low volume, AI agents

Pricing model

getpeppr
Business from EUR 49/mo + usage; Platform plans EUR 99–499/mo
peppol.sh
Pay-per-doc EUR 0.20→0.10, no monthly fee

Cheapest at low volume

getpeppr
—
peppol.sh
Yes — no monthly floor

Official SDK

getpeppr
Published TypeScript SDK + CLI on npm
peppol.sh
TS SDK advertised; npm package not resolvable (2026-06-24); Python/PHP soon

Multi-tenant

getpeppr
Native — one master API key, N legal entities
peppol.sh
Connect tier (from EUR 250 top-up), no per-tenant fee

Identity verification

getpeppr
Multi-registry Trust Layer — VIES, Bolagsverket, KBO/BCE, INSEE
peppol.sh
KYC + VAT validation (not multi-registry)

Dashboard

getpeppr
Yes — management dashboard
peppol.sh
Yes — optional (API-first, not required)

AI-agent / MCP

getpeppr
Not a focus
peppol.sh
Yes — SKILL.md + MCP server

Free sandbox

getpeppr
Yes — free forever
peppol.sh
Yes — free forever

Validation

getpeppr
EN 16931 + Peppol BIS 3.0
peppol.sh
EN 16931 + Peppol BIS 3.0

Delivery webhooks

getpeppr
Yes
peppol.sh
Yes

Time to first invoice

getpeppr
—
peppol.sh
~30 sec

Market focus

getpeppr
Belgium + France + Ireland self-serve · French regulated CTC in pilot · 5 more assisted
peppol.sh
EU (Belgium-based)

Competitor details verified against peppol.sh's public pages and the npm registry on 2026-06-24. Both providers deliver over a certified Peppol Access Point; check each provider's site before deciding.

When peppol.sh is the better choice

peppol.sh is a genuinely strong developer API. It's the better pick when:

  • You're a solo developer or a single company sending your own invoices.
  • Your volume is low or sporadic — pay-per-document with no monthly fee works out cheaper.
  • You want an API-first workflow you can drive entirely from the terminal or an AI agent — peppol.sh doesn't require a dashboard.
  • You want the fastest possible first send (peppol.sh advertises ~30 seconds).
  • AI-agent integration (SKILL.md / MCP server) is a priority for you today.

When getpeppr is the better choice

getpeppr is built for the platform shape — sending on behalf of many customers, with the tooling that requires.

  • You're a SaaS or ERP platform sending Peppol invoices on behalf of many customer legal entities.
  • You need a native multi-tenant model — one master API key, N legal entities, per-tenant authorisation.
  • You need registry-based identity verification against the national business registries (VIES, Bolagsverket, KBO/BCE, INSEE) before a customer can send.
  • You want a published, type-safe TypeScript SDK and CLI on npm today, plus a management dashboard.
  • You prefer predictable subscription pricing as you scale, and white-glove help embedding Peppol.
Start building freeRead the docs

Frequently asked questions

Is peppol.sh cheaper than getpeppr?

At low or sporadic volume, often yes — peppol.sh has no monthly fee and you pay per document (from EUR 0.20 down to EUR 0.10 at higher top-ups). getpeppr starts at EUR 49/month plus usage. getpeppr's value shows up when you're a platform sending for many customer legal entities and want native multi-tenant support, identity verification, a dashboard, and predictable pricing as you scale.

Does peppol.sh have an official SDK?

peppol.sh advertises a TypeScript SDK with code examples, but as of 2026-06-24 the npm package (checked under @peppol-sh/node, @peppol-sh/sdk, and @peppol-sh/peppol) was not resolvable, and Python and PHP are marked coming soon. getpeppr ships a published, type-safe TypeScript SDK (@getpeppr/sdk) and a CLI (@getpeppr/cli) on npm today.

Which is better for a multi-tenant SaaS platform?

getpeppr is purpose-built for it: one master API key, N legal entities, per-tenant authorisation, plus a multi-registry Trust Layer across the national business registries (VIES, Bolagsverket, KBO/BCE, INSEE) that name-checks each legal entity before it can send. peppol.sh supports multi-tenant sending through its Connect tier (which unlocks from a EUR 250 top-up, with no per-tenant fee) and offers KYC and VAT validation, but not getpeppr's multi-registry Trust Layer checks.

Can I migrate from peppol.sh to getpeppr?

Both are JSON-in / UBL-out APIs that deliver over a certified Peppol Access Point, so the integration shape is similar. You map your invoice JSON to getpeppr's schema and onboard your legal entities; the CLI lets you validate invoices offline first, with no account required.

Ready to ship Peppol invoices?

Send your first invoice in minutes. Free sandbox, no credit card, full SDK access.

Start FreeView Documentation
$npm install @getpeppr/sdk

Free sandbox forever. No credit card required. Ship invoices in minutes.