Sending documents by API: A simple introduction

UBL 3.0 in Peppol BIS Billing

Schematron in Peppol BIS Billing 3.0

Adding users

What is a UBL File?

What is CSV?

What types of documents can I upload? 

Do I get error messages for invalid uploads? 

How is submitted content validated? 

How is the file prepared and formatted? 

How do I send documents via SFTP?

Can I have tracking information via API webhook? 

What happens when the receiver can't be reached by PEPPOL? 

What types of reports am I able to generate? 

Can I search and filter inbound e-invoices? 

Can I download inbound e-invoices from Communication Platform?

Can I retrieve inbound e-invoices via additional methods? 

Can I keep track of the events that happened to my document? 

Can I identify what events were done by a user? 

Can I search audit logs?

How can I configure a File Reception Validation Rule?

Creating Email Templates and Using Dynamic Content

Using Groups and Roles

How do I send documents via API? 

Doccle

Release note 1.6

Release CompanyID 

Release note 1.10

Create a workflow

How to enable and configure inbound e-invoicing?

Getting started

What is a UBL File

How can I archive my files (long term)? 

What is JSON?

How can I consult inbound e-invoices from the platform? 

Document Delivery by SFTP

What is SFTP ?

What is XML?

What is API?

Release note 1.5

Release note 1.7

Release note 1.8

How can I easily find my submissions? 

Do I have visibility into the tracability of my documents, both individually and in bulk?

Can I have tracking information via API?

Release note 1.9

Maintenance 27 Aug 2026

Discard channel

Introductions

User management

Everything you need to know to integrate and operate our platform efficiently

Technical information

Understand the supported formats and requirements for submitting your documentsUBL documents

File formats

Core functionalities

Output channels

Input

Sending

Archiving

Reporting

Document flows

e-invoicing

Glossary

Navigation

Support

🚀 Releases notes

An API, or Application Programming Interface, is a set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information. They are essential for enabling integration between different systems and services.API stands for Application Programming Interface. In simple terms, it’s a way for two systems to talk to each other—like giving your software the ability to send instructions directly to our platform.Instead of clicking buttons manually, your system can say:<blockquote>“Here’s a document. Please send it to this customer via email.” And our platform takes care of the rest.</blockquote>Using our API, you can fully automate how business documents—like invoices, payslips, or payment reminders—are prepared and sent, saving time and reducing the risk of human error.<h2>💭 Why Use an API?</h2>Using the API is ideal if you:<ul><li>Generate documents automatically from your own tools (like ERP or CRM systems)</li><li>Want to send large volumes without manual uploads</li><li>Need real-time feedback about delivery statuses</li><li>Prefer a fully automated workflow with little to no human interaction</li></ul><h2>How to Configure Your API in Our Platform</h2>To get started, follow these basic steps:<ol><li>You'll need your ClientID and Secret Token. This can be found under "general settings" in the settings page. We use OAuth, if you want to learn more on that part, check out this article.&nbsp;</li><li>Define your workflow. Before you can start sending, make sure you have created a workflow. Check out this page to discover more on creating and managing workflows.</li><li>Check the documentation to find your workflow unique ID When sending documents by API, you need to reference the workflow you wish to use. You can find the ID in the API documentation on our platform.&nbsp;</li><li>Test and go live We recommend that you test your integration with different scenario's before going live.</li></ol><h2>Discover more</h2><ul><li>Feedback on the progress of your documents can also be send back to your systems by API. Read more about it here.</li><li>Consult our API documentation. Go to the 'Help &amp; Support' section in the bottom left corner <img src="https://cdn-assets.productfruits.com/7f53961c-3813-497f-8dc3-e7b84179eb57"> In the top menu, different categories for API documentation are available: <img src="https://cdn-assets.productfruits.com/ce413082-8be7-4623-b351-2b7b009e6bae"> &nbsp;</li></ul><figure class="table"><table><tbody><tr><td>API Rate limit: please note that API calls are limited to 500 calls par minute for authenticated users, and 100 calls per minute for unauthenticated users.</td></tr></tbody></table></figure>

<h2 class="LexTKB__h2" dir="ltr">What is changing?</h2>This release updates the information used to populate the following section of the generated UBL invoice:<pre class="LexTKB__code" spellcheck="false"><pre class="LexTKB__code" spellcheck="false">&lt;cac:PartyLegalEntity&gt; &lt;cbc:RegistrationName&gt;&lt;/cbc:RegistrationName&gt; &lt;cbc:CompanyID schemeID="0208"&gt;XXXX&lt;/cbc:CompanyID&gt; &lt;/cac:PartyLegalEntity&gt; </pre></pre>Previously, the <code spellcheck="false" style="white-space: pre-wrap;">CompanyID</code> field was always populated using the <code spellcheck="false" style="white-space: pre-wrap;">vatNumber</code> value from the unified JSON.We will now use the <code spellcheck="false" style="white-space: pre-wrap;">enterpriseNumber</code> value when it is available. When <code spellcheck="false" style="white-space: pre-wrap;">enterpriseNumber</code> is not provided, the existing behavior remains unchanged and <code spellcheck="false" style="white-space: pre-wrap;">vatNumber</code> will be used as the fallback value.<h2 class="LexTKB__h2" dir="ltr">Why are we making this change?</h2>Some country-specific invoice flows, particularly in the Netherlands and Germany, expect this field to contain an enterprise or company registration number rather than a VAT number.Using the VAT number systematically could therefore result in data-consistency or validation issues for these flows.<h2 class="LexTKB__h2" dir="ltr">Impact</h2>No action is required from customers who already provide the appropriate <code spellcheck="false" style="white-space: pre-wrap;">enterpriseNumber</code> value in the unified JSON.This update does not affect:<ul class="LexTKB__ul"><li value="1" class="LexTKB__listItem">Peppol participant reachability</li><li value="2" class="LexTKB__listItem">The Endpoint ID used for Peppol routing</li><li value="3" class="LexTKB__listItem">Participant identification on the Peppol network</li><li value="4" class="LexTKB__listItem">Invoice-routing logic</li></ul>The change applies exclusively to the content of the generated UBL invoice document.

<img src="https://cdn-assets.productfruits.com/f6c5af18-4779-4c86-ac9d-9101e6262fce" alt="" data-position="full" data-width="100%" data-height="auto" class="lexical-inline-image position-full" style="z-index: 20;">IntroductionThis release introduces enhanced access management, expanded digital delivery options, and improved authentication reliability to help you manage users more efficiently and securely.What's new<ul class="LexTKB__ul"><li value="1" class="LexTKB__listItem">New role-based user and group management – Administrators can now manage user access through a standardized role catalogue and configurable user groups. Want to know more about Access management, <a href="https://help.enterprise.speos.be/en/article/using-groups-and-roles" rel="noreferrer" class="LexTKB__link">click here</a>.</li><li value="2" class="LexTKB__listItem">Doccle available as a delivery channel – The Communication Platform now supports <a href="https://help.enterprise.speos.be/en/article/doccle" rel="noreferrer" class="LexTKB__link">Doccle as an additional digital delivery channel</a>. Delivery status is available through the Audit Trail, providing better visibility into document delivery and enabling a controlled rollout of the service.</li><li value="3" class="LexTKB__listItem">More reliable SMS verification – SMS verification for multi-factor authentication (MFA) is now powered by a dedicated SMS provider, improving the reliability of login and user verification while strengthening the security and resilience of the platform.</li></ul>

Welcome! We’re glad to have you on board.Our platform is designed to help you manage the entire lifecycle of outgoing business documents—such as invoices, payslips, or official notifications—across digital and physical channels. Whether you’re a small team or a large organization, the platform gives you full control over how documents are delivered and tracked.<h3>How it works — in short</h3>When documents are sent to the platform, a predefined workflow determines how they are processed. A workflow applies logic and rules to make sure each document is handled correctly—then routes it to one or more output channels, such as email, eBox, PEPPOL, or traditional print and post.You are in control: you configure which channels are available, and how the workflow should behave depending on your business needs.<h3>Where to begin</h3>To get started quickly, we recommend the following steps:<ol><li>Invite collaborators Add users to your environment and assign them to the appropriate roles and groups.</li><li>Set up your first output channel Choose how you want your documents to be delivered and configure the necessary channel (email, print, PEPPOL, etc.).</li><li>Create your first workflow Define the basic rules for handling incoming documents—such as routing by document type, department, or priority.</li></ol>Once these are in place, you’re ready to send your first document through the platform!If you need help along the way, our support articles will guide you step by step.

The platform supports long-term archiving of delivered documents. Archiving can be activated per workflow. When enabled, all documents processed through that workflow are automatically archived for long-term retention. Archived documents are visible as part of the document audit trail, and can be accessed through the speos on-demand UI for manual retrieval or via a web service API for automated integration. This helps meet the compliance requirements, improves your accessibility to historical records, and sets a strong foundation for legally compliant document preservation.

You can access, view, and track inbound e-invoices directly from the front-end interface of the e-invoicing platform:You get a centralized dashboard where invoices received through the PEPPOL network can be searched, filtered and inspected using criteria such as a sender, date, status.You can open each invoice to see:<ul class="LexTKB__ul"><li value="1" class="LexTKB__listItem">A pdf version</li><li value="2" class="LexTKB__listItem">The original UBL received from the access point of the sender/supplier</li><li value="3" class="LexTKB__listItem">The attachments</li></ul>

Go back to speos Platform

Was this article helpful?

You recently requested to reset your password for your account. Use the button below to reset it. This password reset is only valid for the next 24 hours.

If you’re having trouble with the button above, copy and paste the URL below into your web browser.

Please check your email for instructions to reset your password.

Check your email

Enter your email address and we will send you instructions to reset your password.

Communication Platform Help Center