The stored files of a care-list invoice with their SHA-256
- In the sandbox
In plain words
Since 0.15.0 a client key with the read scope reads the evidence of its own client's invoices, 10 times a
minute. Another client's invoice answers 404, exactly as an invoice that is not on the care list does. Files over
8 MiB in all answer 413 (evidence-too-large) for every key; read them one by one with
GET /invoices/{id}/documents/{kind}.
apiKeyAuthorizationBearer <token>Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.
id*stringfiles: kind, sha256, file_base64.
application/json- response
curl -X GET "https://example.com/care/string/evidence" \ -H "Authorization: Bearer <your-api-key>"{}Revoke an API key; it stops working at once POST
Previous
The care list: rejected and dead-lettered invoices with the catalogue code and who acts GET
Since 0.15.0 a client key with the read scope reads its own client's rows, so a business can see its own rejected invoices. A client key gets at most its newest 200 rows in the asked status, with truncated: true when there are more; since 0.18.2 the status is applied first, so an old open row is never hidden behind newer handled ones. It may list 30 times a minute (429 past that). The operator's key sees every client's rows, or one client's with client.