Peppol Directory Participants Scraper

Find Peppol participants, verify e-invoicing identifiers, and export compliance-ready business records from the official public Peppol Directory.

What does Peppol Directory Participants Scraper do?

Peppol Directory Participants Scraper extracts participant records from the official public Peppol Directory.

It helps teams find organizations that can receive Peppol e-invoices, verify participant identifiers, and export country or keyword lists for compliance and sales workflows.

The actor uses the public REST API rather than a browser, so runs are fast, predictable, and inexpensive.

Who is it for?

🏢 ERP and e-invoicing vendors use it to build account lists.

💳 AP automation teams use it to verify suppliers before onboarding.

🧾 Compliance consultants use it to document Peppol readiness by country.

📊 B2B data teams use it to enrich company records with participant identifiers.

Why use this actor?

The public Directory is searchable, but repeatable exports are easier with an Apify actor.

You get structured JSON, CSV, Excel, and API access, plus run history, webhooks, scheduled runs, and integrations with your existing Apify workflows.

Data you can extract

The dataset includes participant ID, participant scheme, participant value, business name, alternate names, country code, registration date, websites, additional identifiers, optional contacts, optional document type identifiers, and source URL.

How much does it cost to scrape Peppol Directory participants?

This actor uses pay-per-event pricing.

Each run has a $0.005 start charge and then charges per participant record saved.

Plan tier	Price per Peppol participant	1,000 participants
Free	$0.000029802	$0.03
Starter / Bronze	$0.000025915	$0.03
Scale / Silver	$0.000020213	$0.02
Business / Gold	$0.000015549	$0.02
Platinum	$0.000010366	$0.01
Diamond	$0.00001	$0.01

The input prefill is intentionally small enough for a useful first run while still demonstrating the country search workflow.

How to scrape Peppol Directory participants

Open the actor.

Add keywords, country codes, names, or participant IDs.

Set the maximum participant count.

Decide whether to include document type identifiers and contacts.

Run the actor and export the dataset.

Input options

Use queries for broad search, countries for exact country lists, names for partial business-name matching, participantIds for exact verification, and geoInfo, website, or contact for targeted filters.

Output example

Each row represents one Peppol participant/entity.

Key fields include participantId, businessName, countryCode, registrationDate, websites, identifiers, documentTypeCount, searchType, searchValue, and scrapedAt.

Tips for better Peppol searches

Use ISO country codes such as BE, NL, DE, AT, or DK for large prospecting runs.

Use exact participant IDs for supplier validation.

Enable document type identifiers when you need capability details, but leave them off for compact lead exports.

Integrations

Send results to Google Sheets, Airtable, Make, Zapier, or your own API.

Common workflows include supplier onboarding checks, monthly country monitoring, e-invoicing market mapping, and CRM enrichment for Peppol-capable companies.

API usage

Run the actor through Apify API clients using actor ID automation-lab/peppol-directory-participants-scraper.

Store input as JSON and fetch the default dataset after the run finishes.

Node.js API example

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/peppol-directory-participants-scraper').call({ countries: ['BE'], maxItems: 100 });
const items = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.items[0]);

Python API example

from apify_client import ApifyClient
import os
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/peppol-directory-participants-scraper').call(run_input={'countries': ['BE'], 'maxItems': 100})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items[0])

cURL API example

curl -X POST 'https://api.apify.com/v2/acts/automation-lab/peppol-directory-participants-scraper/runs?token=$APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"countries":["BE"],"maxItems":100}'

MCP integration

Peppol Directory Participants Scraper is available as a tool for AI assistants that support the Model Context Protocol (MCP).

Add the Apify MCP server to your AI client — this gives you access to all Apify actors, including this one.

Claude Code setup

$claude mcp add --transport http apify "https://mcp.apify.com"

Claude Desktop, Cursor, or VS Code setup

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com"
    }
  }
}

Example prompts:

• "Use automation-lab/peppol-directory-participants-scraper to find 100 Belgian Peppol participants."
• "Verify Peppol participant 9915:b and include document type capabilities."
• "Export companies with Government in their Peppol Directory name for compliance review."

Scheduling and monitoring

Schedule the actor weekly or monthly to monitor participant availability by country or keyword.

Use webhooks to notify your compliance or sales systems when new exports are ready.

Legality and source terms

The actor uses the public Peppol Directory search API.

Use the data responsibly, respect the Directory rate limit, and comply with applicable privacy, procurement, and marketing regulations in your jurisdiction.

Troubleshooting

If a query returns no records, try broader keywords or a country search.

If a name search fails, ensure it has at least three characters.

If you see rate-limit warnings, reduce parallel scheduled runs and keep result limits reasonable.

Related scrapers

Explore related Automation Lab actors on Apify for business directories, contact discovery, website checks, and B2B enrichment.

Use https://apify.com/automation-lab/ links when composing workflows.

FAQ

Can I scrape the whole Peppol Directory? The public search API caps browsed results per query, so use country and keyword slices.

Does it require login? No.

Does it use a browser? No, it uses HTTP requests to the official REST API.

Field reference

• participantId — structured Peppol Directory participant data for exports and integrations.

• participantScheme — structured Peppol Directory participant data for exports and integrations.

• participantValue — structured Peppol Directory participant data for exports and integrations.

• businessName — structured Peppol Directory participant data for exports and integrations.

• allNames — structured Peppol Directory participant data for exports and integrations.

• countryCode — structured Peppol Directory participant data for exports and integrations.

• registrationDate — structured Peppol Directory participant data for exports and integrations.

• websites — structured Peppol Directory participant data for exports and integrations.

• identifiers — structured Peppol Directory participant data for exports and integrations.

• contacts — structured Peppol Directory participant data for exports and integrations.

• additionalInfo — structured Peppol Directory participant data for exports and integrations.

• documentTypes — structured Peppol Directory participant data for exports and integrations.

• documentTypeCount — structured Peppol Directory participant data for exports and integrations.

• searchType — structured Peppol Directory participant data for exports and integrations.

• searchValue — structured Peppol Directory participant data for exports and integrations.

• sourceUrl — structured Peppol Directory participant data for exports and integrations.

• scrapedAt — structured Peppol Directory participant data for exports and integrations.

Example inputs

Country prospecting

{"countries":["BE"],"maxItems":100}

Supplier verification

{"participantIds":["9915:b"],"includeDocumentTypes":true}

Keyword search

{"queries":["Austrian Government"],"includeContacts":true}

Support

If you need a new Peppol filter or integration pattern, open an issue on the actor page and include the query you tried, the expected records, and a sample participant ID if available.