# Verify Peppol Participants Before Enabling Routing

**Use case:** 

Check Peppol IDs before configuring supplier or customer e-invoice routing. Replace the sample participants with your own scheme:ID values. Get publication status, serving SMP and advertised document types, with explicit errors for inconclusive checks. Change detection is off: results go to the run dataset without updating monitoring baselines. This does not test invoice delivery.

## Input

```json
{
  "participants": [
    "9925:BE0848934496",
    "0192:930280070",
    "0208:0891323496"
  ],
  "network": "production",
  "monitorChanges": false,
  "emitUnchanged": true
}
```

## Output

```json
{
  "participant_id": {
    "label": "Participant identifier",
    "format": "string"
  },
  "participant_scheme": {
    "label": "Identifier scheme code",
    "format": "string"
  },
  "participant_value": {
    "label": "Identifier value",
    "format": "string"
  },
  "network_status": {
    "label": "Network publication status",
    "format": "string"
  },
  "smp_url": {
    "label": "Serving SMP",
    "format": "string"
  },
  "document_types": {
    "label": "Document types",
    "format": "array"
  },
  "document_type_count": {
    "label": "Document type count",
    "format": "integer"
  },
  "fingerprint": {
    "label": "State fingerprint",
    "format": "string"
  },
  "scraped_at": {
    "label": "Observed at",
    "format": "string"
  }
}
```

## About this Actor

This example demonstrates how to use [Peppol Participant Lookup & Change Monitor](https://apify.com/automa-flow/peppol-network-reachability-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/automa-flow/peppol-network-reachability-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/automa-flow/peppol-network-reachability-monitor.md

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).