Whether you’re a small business, a large enterprise, or a software vendor, Qvalia’s API gives you a single, standards-based way to integrate with the Peppol network, with optional support for additional EDI flows, intelligent document processing, and data enrichment.

The same API can:

In this guide, you will learn how to:

Qvalia’s API provides a unified interface for electronic business messages over Peppol and EDI. It is built to support core scenarios such as:

Common design principles across all of this:

For you, this means you can think in terms of business messages instead of networks and protocols. You create valid UBL-based documents; Qvalia handles the Peppol and EDI layer in the background.

Getting started with Qvalia’s Peppol API requires only a few basics:

Once these elements are in place, you are ready to start testing Peppol traffic with Qvalia.

This section walks through a typical first integration between your system and Qvalia’s Transaction API, covering both sending and receiving Peppol invoices.

Begin by integrating against the sandbox environment:

This lets you build and test without affecting real customers or financial flows.

In your configuration, store:

Each request should include:

All transactions use UBL 2.1 as the underlying standard.

You can either:

Headers control the format:

This flexibility allows you to integrate the Peppol API into both JSON-first and XML-first environments.

Next, map your internal invoice model to UBL elements:

The goal is to ensure that:

You then serialize this as either JSON or XML, depending on your format choice. For incoming invoices, you use the same UBL structure when reading, validating, and mapping data from Qvalia into your internal model.

Step 5a: Send an outgoing Peppol invoice

With your outgoing payload ready:

Include:

Qvalia validates the invoice, routes it via the Peppol network or EDI/VAN, and returns a response with identifiers and status.

To retrieve incoming invoices from Qvalia via API, you typically:

Optionally, you can:

The returned UBL JSON or XML is then mapped into your internal data model for posting, approval, or further processing.

The Transaction API uses predictable HTTP status codes that you can map to logs, monitoring, and user messages. Typical patterns:

The same patterns apply whether you are sending or receiving invoices.

In addition to the API responses, you can always log in to Qvalia and review activity in the transaction log. This gives you a UI-based view of what is happening in your integration, including, for example:

The transaction log is useful for:

Together, the HTTP status codes and the transaction log provide a complete picture: your system can react programmatically to responses, while your team can investigate and follow up directly in Qvalia when needed.

Once you have invoices in place, it is straightforward to extend your integration to a full Peppol message portfolio.

Typical extensions include:
Purchase orders. Receive and send structured orders electronically
Order responses and changes. Confirm, modify, or cancel orders
Catalogues. Maintain product and price information in electronic catalogues
Despatch advice. Communicate shipment information
Message-level responses. Track technical and business-level acknowledgements

Because all of this uses the same API design, authentication model, UBL 2.1 data model you do not need separate projects or gateways for each document type. You enable new use cases as your business or your customers’ requirements evolve.

This is where the “one Peppol API regardless of need” promise becomes tangible: the same integration serves small suppliers, large enterprises, and complex platform scenarios.

If you are a software vendor — operating an invoicing platform, ERP, accounting solution or integration platform— your requirements are slightly different. You need to:

For example:

Qvalia routes and receives messages as if they were sent or received directly by the customer, with full traceability per account.

In addition to transport and connectivity, Qvalia also offers the Enrichment API, which can enrich transactions with line-item classification, pre-posting, and more, and also extract and transform PDF documents into rich, structured, and validated data with minimal effort.

The Enrichment API is designed as an asynchronous service:

This result can include:

A typical integration looks like this:

In all cases, access to this technology is straightforward: the same account and security model as Transaction API, and a small set of well-defined endpoints.

Qvalia’s API is built to give you simplified, scalable access to the Peppol network, regardless of your company type:

Your next step is straightforward: connect to the sandbox, send your first test invoice, and start planning how Peppol, EDI, and enrichment can become a built-in part of your operations or product — rather than a separate, complex project.