Introduction
peppol.sh is a Peppol e-invoicing API designed to help businesses send compliant e-invoices without managing the Peppol network themselves. Instead of struggling with UBL schemas, SMP lookups, or access point setup, developers can make a simple API call with JSON data and let peppol.sh handle conversion and delivery.
What is peppol.sh?
peppol.sh is a Peppol e-invoicing API and an API-first e-invoicing service for the Peppol network. It solves a real problem: Peppol e-invoicing requires validation, registration, and communication with certified access points. peppol.sh wraps that entire process into one REST API call.
The service accepts JSON payloads, converts them to Peppol BIS 3.0 UBL, validates documents against EN 16931, and delivers them through the Peppol network. It also includes a sandbox environment from signup, so users can send Peppol invoices immediately and test integration before going live. This makes peppol.sh more than a simple conversion tool: it is a complete Peppol e-invoicing API for modern software teams.
Why does this matter? European e-invoicing mandates are expanding. ViDA will require structured e-invoicing across the EU by 2030, and several member states already enforce it today. For software teams, this means they need a reliable way to add e-invoicing compliance without becoming Peppol experts. peppol.sh targets that gap.
Key Features of peppol.sh
The main strength of this Peppol e-invoicing API is that every process is automated.
One-call document sending
Send a JSON payload to the /v1/documents endpoint and the document is queued for delivery. No multi-step flows, no manual Peppol configuration. This is the core of the Peppol e-invoicing API experience.
JSON to UBL conversion
peppol.sh converts JSON into valid Peppol BIS 3.0 UBL automatically. This removes the need to learn UBL syntax or maintain complex transformation templates.
Built-in e-invoicing compliance
The service handles EN 16931 validation and operates as a certified Peppol access point. This makes it easier to meet e-invoicing compliance requirements in the EU.
Sandbox from day zero
Every account starts in sandbox mode. Developers can send Peppol invoices with a ps_test_ key, and sandbox deliveries are sent by email. No UI, no approval, no credit card.
Delivery tracking and webhooks
Every document has a status endpoint, and webhooks notify delivery events. Teams can check whether each invoice actually reaches the recipient.
Participant lookup
A lookup endpoint lets you check whether a company is registered on Peppol before sending. This helps avoid failed deliveries.
Stripe app for automatic sending
For Stripe users, the official app listens to invoice.finalized events and sends the invoice through the Peppol network automatically. No code changes are needed for this route.
AI-agent ready
peppol.sh includes an SKILL.md file and MCP server, so AI agents can create accounts, send invoices, and track delivery autonomously. This fits the API-first design.
Use Cases for peppol.sh
SaaS and e-commerce checkout
After a customer pays, the system can send Peppol invoices to their business through peppol.sh. This is useful for SaaS products, e-commerce stores, and service businesses.
Accounting and ERP integration
Accounting platforms can embed Peppol sending into their product. Each tenant gets one Company identity, but there are no per-tenant fees or monthly minimums.
Automated billing workflows
Finance teams and developers can build fully API-driven billing flows. From signup to KYC to live sending, every step can be automated.
AI agents and internal tools
Because the entire API is bootstrappable, AI agents or internal scripts can create workspaces, send invoices, and check status without opening a dashboard.
How to Use peppol.sh
Using this Peppol e-invoicing API is built around a few simple steps.
- Create an account with one curl request to
/v1/signupand get a sandbox API key instantly. - Use the
ps_test_key to send Peppol invoices in sandbox mode and confirm the response includes a document ID. - Complete KYC by uploading and submitting documents via
/v1/kyc/documentsand/v1/kyc/submit. - Create a live API key and start sending invoices through the certified Peppol access point.
No browser is required. The whole flow can be done from the terminal or an automated agent.
Target Audience for peppol.sh
- Developers who want a Peppol e-invoicing API without managing infrastructure
- SaaS and e-commerce businesses
- Accounting and ERP platforms
- Billing providers and fintech companies
- AI agent builders and automation teams
- Companies preparing for EU e-invoicing mandates
Is peppol.sh Free?
peppol.sh offers a free sandbox environment and transparent pay-per-document pricing for live sending.
| Plan | Price | Features |
|---|---|---|
| Sandbox | Free | Unlimited test invoices, email delivery, API access |
| Live | From €0.10 per invoice sent | No monthly minimum, no per-tenant charges |
This pricing structure makes the Peppol e-invoicing API accessible to small teams and large platforms alike. No credit card is required at signup, and credits never expire.
peppol.sh's Pros and Cons
| Aspect | Pros | Cons |
|---|---|---|
| Ease of use | Simple JSON API, no UBL knowledge needed | Requires some technical skill for API integration |
| Compliance | EN 16931 validation, certified access point | Focused on European Peppol requirements |
| Pricing | Pay per document, free sandbox forever | Costs can add up at very high invoice volume |
| Onboarding | Fully API-driven, no dashboard required | Less useful for non-technical teams |
| Automation | Webhooks, AI-agent ready, Stripe app | Some features need additional setup |
Frequently Asked Questions about peppol.sh
How long does it take to start using a Peppol e-invoicing API?
Signup is instant via API. Test invoices can be sent within a minute in sandbox mode. Going live requires KYC approval and workspace verification, but there is no dashboard or approval step for signing up.
Does peppol.sh work with any EU country?
peppol.sh is built around the Peppol network and Peppol BIS 3.0, which is widely used in Europe. Buyers and suppliers must be registered on Peppol to send and receive invoices through the network. A lookup endpoint helps check registration by name or tax ID.
What is the difference between sandbox and live keys?
Sandbox keys start with ps_test_ and deliver test invoices by email. Live keys start with ps_live_ and deliver invoices through the real Peppol network. Workspace verification is done once, and live keys are created after approval.
Can I send PDF invoices through peppol.sh?
Yes. The Peppol e-invoicing API supports JSON and PDF upload as two ways to send compliant documents. JSON is converted to UBL, and PDFs are submitted as documents, according to the product documentation.
Is there a free plan for testing?
Yes. Every account starts in sandbox mode and stays free forever for testing. Users can send test documents in the sandbox before creating a live workspace.
Does peppol.sh charge per tenant?
No. There are no per-tenant fees and no monthly minimum. Pricing is based on the number of invoices sent, starting at €0.10 per invoice.
peppol.sh Tags
Peppol e-invoicing API, send Peppol invoices, JSON to UBL, Peppol BIS 3.0, e-invoicing compliance, Peppol access point, e-invoice API, sandbox testing, Stripe e-invoicing, EU e-invoicing mandates, automated e-invoicing, API-first e-invoicing
