---
title: "PEPPOL lookup"
method: GET
path: "/einvoice_search"
tags: ["E-invoicing search"]
---

# PEPPOL lookup

`GET /einvoice_search`

## Request

- Base URL: `https://api.sandbox.monite.com/v1`
- URL: `https://api.sandbox.monite.com/v1/einvoice_search`
- Auth: HTTP bearer

Checks if the specified VAT number or business number is registered on the PEPPOL network as a receiver. For example, you can use this endpoint to check if an entity's counterparts are registered in PEPPOL before creating e-invoices for those counterparts.

The lookup is powered by PEPPOL SMPs (Service Metadata Publishers) so it also includes registrations that are not visible in the public PEPPOL directory.

Both partner tokens and entity user tokens can be used for authentication.

Production and sandbox lookups are separate.

## Query parameters

- `network_identifier` string, required
- `network_schema` 'DE:VAT' | 'NL:KVK' | 'NL:VAT' | 'BE:VAT' | 'BE:EN', required

## Headers

- `x-monite-version` string, required

## Response `200`

Successful Response

- CounterpartEinvoicingCredentialExistenceResponse
  - `exists` boolean, required: `true` is the specified identifier is registered as a receiver in PEPPOL, and `false` otherwise.

## Other responses

- `401`: The `Authorization` header is missing or contains an invalid or expired access token. See [Authentication](https://docs.monite.com/api/concepts/authentication) to learn how to authenticate API calls.
- `422`: Possible reasons: * A required query parameter was not provided. * Invalid or unsupported `network_schema`.
- `429`: API rate limit has been exceeded. Check the response headers for the rate limit information.

---

[API](https://skmtc.dev/monite/apis/monite-2.md) - [All operations](https://skmtc.dev/monite/apis/monite-2/llms.txt) - [OpenAPI document](https://skmtc.dev/monite/apis/monite-2/revisions/4299ccf95edb?raw)