PEPPOL API
Overview
Section titled “Overview”The PEPPOL API lets external systems send and receive PEPPOL documents, validate XML, look up participants, and subscribe to webhooks — without using Invoice Manager for every message.
Full method list: REST API Reference.
Concepts: PEPPOL Overview.
Enabling access
Section titled “Enabling access”- Confirm your subscription plan allows API / PEPPOL automation.
- Create an integration User with least-privilege roles.
- Generate API keys for that user.
- Restrict Legal Entity User Permissions if needed.
Authentication
Section titled “Authentication”Authorization: token {api_key}:{api_secret}Core methods
Section titled “Core methods”| Capability | Method path |
|---|---|
| Send XML or Factur-X PDF | tapr_next.api.peppol.transmission.send_peppol_invoice |
| Create SI from XML and send | tapr_next.api.peppol.transmission.send_invoice |
| Check status | tapr_next.api.peppol.transmission.check_status |
| Validate XML | tapr_next.api.peppol.transmission.validate_xml |
| Receive (API storage) | tapr_next.api.peppol.inbound.receive_peppol_message |
| List / get received | get_received_invoices / get_received_invoice (full invoice: header, totals, items, charges, taxes; include_xml=1 adds the raw XML) |
| Confirm posted | confirm_invoice_posted |
| SMP lookup | lookup_participant |
| Configure webhook | tapr_next.api.peppol.webhooks.configure_webhook |
Call via POST/GET /api/method/<path>.
Webhooks
Section titled “Webhooks”Event types:
- Invoice Received
- MLR Received
- All
Auth: none, bearer, API key header, basic auth. Optional HMAC signing. HTTPS only; private IP ranges blocked (SSRF protection). System Manager only for configuration.
Metering
Section titled “Metering”Send and some lookup/validate endpoints are metered against plan quotas. Monitor Tapr Settings → Subscription.