Platform integration
One integration. Every customer on Peppol. getpeppr handles identity verification, customer authorisation, and network delivery — your platform stays focused on your product.
Built for SaaS platforms
If your customers invoice their own clients, getpeppr lets your platform put every one of them on the Peppol network — through a single integration. You connect once with one master API key. From there you create a Peppol legal entity for each customer, send invoices on their behalf, and receive status webhooks.
We carry the hard parts: KYB verification against official business registries, customer authorisation, Peppol network registration, UBL generation, and BIS 3.0 compliance. Your platform never touches XML and never runs a Peppol access point.
curl https://api.getpeppr.dev/v1/legal-entities \
-H "Authorization: Bearer sk_live_your_master_key" \
-H "Content-Type: application/json" \
-d '{
"externalId": "customer_8412",
"companyName": "Bright Health Ltd",
"country": "GB",
"address": { "line1": "10 King Street", "city": "London", "zip": "EC2V 8EA" },
"identifier": { "scheme": "GB:CRN", "value": "12345678" }
}'What getpeppr handles
Every customer you onboard moves through the same managed pipeline. You drive it with simple API calls; we do the regulated work behind each step.
- Identity verification (KYB) — each customer's legal identity is checked against the official business registry of their country before activation.
- Customer authorisation — your customer attests, on a getpeppr-signed and audited page, that they authorise invoicing on their behalf. Required for production; captured as evidence.
- Network registration — we register each verified, authorised identity on the Peppol network (SMP provisioning).
- Validation & delivery — UBL 2.1 generation, Peppol BIS 3.0 business rules, and AS4 delivery to the recipient's access point.
- Lifecycle webhooks — your platform is notified at each meaningful transition, so your UI stays in sync without polling.
Master API keys
A standard getpeppr key manages one company's invoicing. A master key
manages many. It carries the standard scopes plus a legal_entities:* set,
so a single key provisions, authorises, and bills for all your customers — with strict
tenant isolation and a per-action audit trail.
404, never another platform's data.
// A master key carries the standard scopes, plus:
legal_entities:create // provision a customer's Peppol identity
legal_entities:list // list the customers you manage
legal_entities:attest // request a customer's authorisation
legal_entities:send_as // send invoices on a customer's behalf
legal_entities:archive // off-board a customerCountry coverage
Before a customer goes live, getpeppr verifies their legal identity against the official business registry of their country. Registry verification is live today for:
| Country | Registry | Status |
|---|---|---|
| 🇬🇧 United Kingdom | Companies House | Live |
| 🇫🇷 France | VIES (SIRENE / SIRET) | Live |
| 🇩🇪 Germany | VIES (VAT) | Live |
| 🇧🇪 Belgium | VIES (enterprise no.) | Live |
| 🇸🇪🇩🇰🇳🇴🇫🇮 Sweden & Nordics | Bolagsverket & national registries | Rolling out |
Coverage expands continuously. Tell us the countries your customers operate in and we'll confirm where we are — and what's next on the map.
Getting platform access
Platform integration runs under a platform agreement — the same footing every serious e-invoicing partner expects. Three steps to live:
- 1. Sign — we put a platform agreement in place (data processing agreement + order form).
- 2. Enable — we enable platform mode on your getpeppr account.
- 3. Generate — you create your master API key in the console and go live.