Peppol API For Invoice Automation
Submit UBL invoices with one endpoint, track delivery via webhooks, and send via Peppol or KSeF with transparent volume pricing.
After creating your account, contact support to enable the Peppol API for your company.
Single Submission Endpoint
Send one base64-encoded UBL XML invoice per request via POST /v1/peppol/invoice.
Immediate Status Response
Get a direct response with submissionId and status set to sending or failed.
Asynchronous Webhook Tracking
Receive lifecycle updates through webhook callbacks as the invoice moves through the network.
OpenAPI-First Integration
Start from Swagger UI or raw OpenAPI JSON and ship your first integration quickly.
API references
Swagger UI
Explore request and response schemas and test directly from your browser.
https://api.budgetinvoice.com/docs/peppolOpenAPI JSON
Import the raw schema into Postman, Insomnia, or your code generator.
https://api.budgetinvoice.com/docs/peppol/openapi.jsonSubmission endpoint
Authenticated endpoint for one UBL invoice per call.
POST https://api.budgetinvoice.com/v1/peppol/invoicecurl --request POST \
--url 'https://api.budgetinvoice.com/v1/peppol/invoice' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"xml": "BASE64_ENCODED_UBL_XML",
"targetNetwork": "auto"
}'Use your API key in the Authorization header. The API returns immediate status and an optional error message.
Webhook delivery updates
After an accepted submission, your configured webhook receives status transitions such as sending, delivered, or failed.
- Configure production and test webhook URLs in your Peppol API settings.
- Callbacks include submissionId, filename, targetNetwork, recipient, status, and updatedAt.
- Handle retries idempotently by using submissionId as your unique key.
- Inspect and resend failed callback deliveries from webhook history in the dashboard.
Webhook best practice
Use HTTPS endpoints and log non-2xx responses for reliable retries.
Example callback payload
JSON{
"submissionId": "bd9f47f3-7bc4-4760-a1dc-8c33df6496f3",
"filename": "invoice-2026-0001.xml",
"status": "delivered",
"targetNetwork": "peppol",
"recipient": {
"scheme": "iso6523-actorid-upis",
"id": "0208:123456789"
},
"updatedAt": "2026-02-28T09:42:11.202Z"
}Volume Pricing For API Submissions
No separate API surcharge. Pay per submitted invoice.
Volume Tiers
Per invoice excl. VAT
- No minimum volume
- Pay per invoice
- Peppol registration included
- Invoice receiving and forwarding included
- No monthly fees
Everything you need to go live
Use the OpenAPI spec, test with the provided samples, and monitor asynchronous delivery via webhooks.
Frequently asked questions
How do I authenticate with the Peppol API?
Send your API key as a Bearer token in the Authorization header. Requests without a valid key return an authorization error.
What format does the invoice endpoint accept?
The endpoint accepts one base64-encoded UBL XML document per request. ZIP files are not accepted on this endpoint.
When do I receive webhook callbacks?
Callbacks are sent when a submission status changes. Typical values are sending, delivered, and failed.
Can I choose the target network?
Yes. Use targetNetwork with values auto, peppol, or ksef. If omitted, auto is used.
Launch your Peppol API integration
Use the OpenAPI spec, test with the provided samples, and monitor asynchronous delivery via webhooks.