Search network

Great API
including webhooks

Simple integration. We offer a clear interface that lets you start sending and receiving documents within a few hours.

View API documentation

Your application gains access to:

  • Verify whether the recipient uses PEPPOL
  • Send documents in various formats
  • Receive documents
  • Track document statuses
  • Convert between formats
  • Notifications about new documents

Two environments ready
for smooth development

To make integration with your SaaS as safe and fast as possible, we have separated testing from live operation. You get two independent environments tailored to the needs of your development cycle.

Sandbox (Test environment)

Ideal for development, experimentation and stress-free testing. The sandbox lets your developers explore the API, configure webhooks and test the application without risk or unnecessary administration.

  • Start immediately: There is no need to wait for account approval or complete a verification process. Register and start testing straight away.
  • Connected to the Peppol test network: The sandbox is more than an isolated simulation. It is connected to the official Peppol test network, so you can send test e-invoices to other test Access Points and verify end-to-end delivery.
  • The sandbox is completely free: Messages sent in the sandbox are free of charge. Send as many test requests as your development team needs.

Production (Live environment)

Real business transactions with maximum security. Once your integration is complete and tested, switch your application to the production endpoint. This is where your customers run their day-to-day business.

  • Live data only: The production environment is reserved exclusively for real e-invoices with legal effect.
  • Thorough customer verification: Peppol’s strict security standards and legal requirements mean that entities must undergo genuine identity verification before using production. This ensures that every sender is fully trustworthy.
  • Guaranteed availability and support: The production API runs on highly available infrastructure with a guaranteed SLA, helping your clients’ invoices arrive on time.

Integration scenarios for connecting

The API supports several integration models. Choose the one that best fits your product and operational needs.

I develop custom applications

If you are building an application for yourself or a single client and want to send or receive documents, use an API key with access to one participant (company).

Use the authorisation endpoint /api/auth/token to exchange client_id/client_secret for a Bearer token (more information).

Use the simplified sending endpoints:
/api/documents/send?wait-for-result or /api/documents/send/isdoc?wait-for-result

Related links: Documentation | Example

I run an accounting firm

Use an API key with access to all participants (companies) and send documents through participant-scoped routes.

Use the authorisation endpoint /api/auth/token to exchange client_id/client_secret for a Bearer token (more information).

Sending endpoints:
/api/participants/{PARTICIPANT_ID}/documents/send?wait-for-result or /api/participants/{PARTICIPANT_ID}/documents/send/as/isdoc?wait-for-result

PARTICIPANT_ID can be:

  • ext:YOUR_IDENTIFIER
  • Peppol ID (for example 9929:12345678)
  • a UUID assigned by our platform

Related links: Documentation | Example

I am a developer and SaaS vendor

A typical flow is to offer “Send invoices via Peppol” in your application, redirect the user to OAuth consent, and then use the issued refresh token to send or receive documents on the user’s behalf.

Next, add an application in the Developers section and configure the required permissions.

Then use the simplified sending endpoints:
/api/documents/send?wait-for-result or /api/documents/send/isdoc?wait-for-result

Related links: Documentation | Example

I develop invoicing SaaS products

For accounting, invoicing or data-capture systems, onboarding is often easier when clients do not have to create an account manually and then return to grant access. You can create client accounts automatically and start verification directly from your application. Common options are:

  • You already know each client and perform verification (KYC) through your own contractual process.
  • You create the account and Dativery completes verification, for example through Bank iD or another method.

In Slovakia, receipt must be confirmed on the Financial Administration portal during verification. In this model, you create an API key, create the individual clients, and then send documents under their participants.

Related links: Documentation | Example

I use a simple application without a backend

Use the “Send via Peppol” button component. It lets you send documents without your own backend; the user is prompted to sign in during the flow.

Related links: Documentation | Example

Let’s discuss the integration

Book a no-obligation call with our technical consultant. We will review your application architecture and show you the best way to integrate the engine.

Schedule a meeting

Recommended links to the documentation

Start sending documents Authorisation methods (API key and OAuth) SaaS onboarding flow Developers section for application setup Complete OpenAPI documentation Directory search component Send via Peppol button component