Invoices received and rejected per day and route
- In the sandbox
In plain words
Worked out from the store on each call. received counts invoices by the UTC day they arrived; rejected counts
invoices now rejected by the UTC day of their last change. A day with nothing has zeros, so a chart has no gaps. Scoped like GET /invoices.
apiKeyAuthorizationBearer <token>Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.
days?integerHow many UTC days, ending today.
1 <= value <= 9030route?array<>One or more routes, comma-separated. All five when left out.
client?stringAs on GET /invoices.
^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$One row per day and route, oldest day first.
application/json- response
generated_at*stringdate-timedays*integerdata*array<>curl -X GET "https://example.com/invoices/series" \ -H "Authorization: Bearer <your-api-key>"{ "generated_at": "2019-08-24T14:15:22Z", "days": 0, "data": [ { "date": "2019-08-24", "route": "PEPPOL", "received": 0, "rejected": 0 } ]}Download a generated document or the route's receipt GET
Kinds: canonical (the JSON as received), erp-export (an ERP export as the ERP sent it), the file as sent (ubl, cii, fa3, pdf), the built document (xrechnung-ubl for Germany, ubl or fa3 otherwise), validation-report and manifest (the SHA-256 of the bytes that go to the route, and the layers that checked them). The four JSON kinds are served as application/json. The ETag is the SHA-256.
List and search invoices GET
A client key sees its own client's invoices; the operator sees every client's, or one client's with client. Rows carry what GET /invoices/{id} carries, without documents, and no invoice content: no buyer or amounts, and no issue date (for Romania and Poland the deadline_at follows from it, to within a few days). An unknown parameter answers 400.