Peppol Discovery

Overview

The Peppol Discovery API enables you to discover if a business is registered on the Peppol network and can receive electronic invoices. This endpoint queries the Peppol Service Metadata Publisher (SMP) to verify if a participant identifier is registered.

Base URLs:

  • Production: https://api.myazur.app

  • Sandbox: https://api-sandbox.myazur.app

Authentication: Requires Bearer token authentication with appropriate folder permissions.


Endpoint

Discover Peppol Participant

Check if a business participant is registered on the Peppol network.

Endpoint: POST /folders/{folder_id}/discoveries

Required Role: User must have discovery creation permission for the specified folder

Path Parameters:

Parameter
Type
Required
Description

folder_id

integer

Yes

The folder ID

Request Body:

Field
Type
Required
Description

scheme

string

Yes

The participant identifier scheme code

identifier

string

Yes

The participant identifier value

Common Identifier Schemes:

Scheme
Country
Description
Example Identifier

9938

Luxembourg

Luxembourg business registration

LU01010101

9925

France

SIRENE number

12345678901234

9907

Italy

Italian VAT number

IT12345678901

9930

Germany

German VAT number

DE123456789

0106

Netherlands

Chamber of Commerce

12345678

0208

Belgium

Enterprise number

0123456789

Example Request:


Response

Example Success Response (200 OK):

Example Not Found Response (200 OK):

Status Codes:

  • 200 OK - Request processed successfully (check code field for registration status)

  • 400 Bad Request - Invalid request (missing folder company or legal entity)

  • 403 Forbidden - Valid license required

  • 404 Not Found - Folder not found


Error Responses

403 Forbidden - No Valid License

404 Not Found - Folder


Use Cases

1. Pre-Invoice Validation

Before sending an electronic invoice, verify that the recipient can receive Peppol documents:

If the response is {"code": "OK"}, the business can receive Peppol invoices.

2. Onboarding New Customers

During customer onboarding, check if they're Peppol-enabled to determine the appropriate invoicing method.

3. Bulk Validation

Validate multiple business partners by making sequential discovery requests to identify which can receive electronic invoices.


Integration Example


Notes

  1. Response Interpretation: Always check the code field in the response. OK means the participant is registered, NOK means they are not.

  2. Identifier Format: Ensure you use the correct scheme code and identifier format. Incorrect formats may return NOK.

  3. Real-time Check: This performs a live lookup against the Peppol SMP registry.

  4. License Validation: Discovery operations require an active license. Expired or disabled licenses will return 403.

Last updated