VAT & Tax

Check e-invoicing readiness for many companies

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.

post/peppol/batch

Request

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

Request body

identifiersstring[] required

IČO values, 6–8 digits each. An empty list is a 400.

Response

E-invoicing status keyed by IČO

object required

Changes

No recorded changes to this operation across all 1 revision of this API.