Mark an invoice's care rows handled
- In the sandbox
In plain words
The operator's key only. Handling a care row is Rejection Care's work, so a client key gets 403.
apiKeyAuthorizationBearer <token>Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.
id*stringThe invoice's care rows, now handled.
application/json- response
curl -X POST "https://example.com/care/string/handled" \ -H "Authorization: Bearer <your-api-key>"{}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.
One credential, without its value GET
Next