---
title: "Check e-invoicing readiness for many companies"
method: POST
path: "/peppol/batch"
tags: ["VAT & Tax"]
---

# Check e-invoicing readiness for many companies

`POST /peppol/batch`

## Request

- Base URL: `https://api.apino.sk/api/v1`
- URL: `https://api.apino.sk/api/v1/peppol/batch`
- Auth: HTTP bearer

The same answer as `GET /peppol/{ico}`, for up to **100** IČO in one call.

This is the shape the question is actually asked in: an accounting office with
a hundred and forty clients needs to know which of them can be invoiced in
January, not one at a time.

Every identifier you send gets a key in the response, as the eight-digit IČO:
a six- or seven-digit one is padded with leading zeros (`123456` comes back
under `00123456`), which is how the registers store it.

A company in the register that the Financial Administration's lists do not
carry — so there is no DIČ to address it by — comes back as an object with
`in_register: true`, no `dic` and `peppol.checked: false`: known, but not
askable. `null` means only that the IČO is in neither the register nor those
lists.

Companies the stored nightly sweep does not already have on the network are
re-checked live during the request, so a company that registered this morning
is reported as reachable rather than as yesterday's absence.

## Request body

- object
  - `identifiers` string[], required: IČO values, 6–8 digits each. An empty list is a `400`.

## Response `200`

E-invoicing status keyed by IČO

- object

## Other responses

- `400`: Validation error
- `401`: Missing or invalid API key
- `429`: Rate limit exceeded

---

[API](https://skmtc.dev/apino/apis/apino-api.md) · [All operations](https://skmtc.dev/apino/apis/apino-api/llms.txt) · [OpenAPI document](https://skmtc.dev/apino/apis/apino-api/revisions/d172569847cd?raw)