REST-API · POST /check/batch · paid route
This route checks up to 1,000 identifiers in a single call. It is suited to checking your whole supplier or customer base regularly, for example once a month.
Every identifier is checked as with POST /check. The results come back in the same order in which you sent the identifiers.
Request
Address: POST https://invoicepress.de/wp-json/einvoice-api/v1/check/batch
Key: Send your API key in the header Authorization: Bearer <key>. Without a valid key the route answers with status 401.
Body: The body of the request is JSON with the field items: a list with up to 1,000 entries, each as with POST /check with scheme, value and optionally context.
Answer
results – One result per identifier, in the same order, each with the same fields as with POST /check.
status – valid, invalid, or unknown when the register gives no answer at the moment.
Status 400 – The list is empty or has more than 1,000 entries.
Status 401 – The key is missing, unknown or blocked.
Status 429 – The batch would exceed the remaining quota. Then nothing is checked and nothing is counted.
Example
curl -X POST "https://invoicepress.de/wp-json/einvoice-api/v1/check/batch" \
-H "Authorization: Bearer <key>" \
-H "Content-Type: application/json" \
-d '{"items":[{"scheme":"vat","value":"DE136695976"},{"scheme":"lei","value":"529900T8BM49AURSDO55"}]}'
Cost
This route is a paid route. Every identifier checked counts as one identifier check against the monthly quota of your plan. To try it, there is the free plan “Free” with a key of your own; it covers about two identifier checks a day. Answers with an error status are not counted.
A batch is accepted or rejected as a whole. Every identifier is counted on its own: a batch with 100 identifiers counts 100 identifier checks.