ApivomApivom
Get Demo

Peppol Directory Participant Search API

Search the OpenPeppol Directory for e-invoicing participants by participant id, name, country or free text and learn which document types they can receive — the pre-flight check for every Peppol e-invoice.

What you can do

  • Find a trading partner's Peppol participant identifier (e.g. 0208:…, 9930:…) from its name or country
  • Confirm the document types and process profiles the receiver supports before you send
  • Free-text and geo-filtered search for supplier and customer onboarding
  • Official OpenPeppol source — no scraping, no third-party copies
  • Per-tenant key, prepaid pricing and full query logging through Apivom Atlas

Use cases

  • Pre-send receiver validation — Look up the customer's participant id and supported document types in your invoicing workflow so the access point never rejects an invoice for an unknown receiver.
  • Supplier onboarding — During vendor registration, search by name and country, store the Peppol id on the supplier record and flag suppliers that are not yet reachable.
  • Mandate readiness audits — Batch-check your customer base against the directory to see who can already receive Peppol invoices ahead of national e-invoicing mandates.

Peppol is the network behind mandatory B2B and B2G e-invoicing across Europe, Singapore, Australia and beyond. Before an invoice can be sent, you need the receiver's participant identifier and proof that it is registered for the right document type. Apivom Atlas exposes the OpenPeppol Directory search as a REST route: pass a participant id, a name, a country code or a free-text query and receive the matching participants with their identifiers, names, countries and supported document types. Responses are cached so repeat checks are free, and every lookup is logged in your Atlas portal next to your other registry queries.

Code sample

Replace YOUR_KEY with the API key issued in Apivom Atlas and run it from your backend.

curl -X POST https://atlas.apivom.com/one/api/ext/openpeppol-directory/v1/query/search \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":{"name":"Apivom","country":"TR"}}'
Authentication

Per-tenant API key (x-api-key header) issued in Apivom Atlas. No upstream account or credential is needed — the public source is called server-side; prepaid balance, per-query pricing.

Frequently asked questions

Which identifiers does the search understand?

Any Peppol participant identifier in scheme:value form (for example 0208 for Belgian enterprise numbers or 9930 for German VAT ids), as well as names, ISO country codes, free text and geographic information.

Does a hit mean I can send any document?

No — check the document types listed on the participant. A receiver registered for UBL invoices only will reject credit notes or orders; the response tells you exactly what it accepts.

How is the API billed?

Prepaid and per query: you top up a balance in Apivom Atlas and each successful query debits the route price shown there. Identical repeat queries are served from the server-side cache free of charge ("cached": true in the response); add ?force=true to refresh at the route price. HTTP 402 means the balance needs a top-up.

How do I authenticate and where do I see my usage?

Every request carries your tenant API key in the x-api-key header; keys are issued and rotated in Apivom Atlas. The portal logs every query with the full request and response payload, so finance and engineering share one audit trail.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.