Revoke an API key; it stops working at once
- In the sandbox
In plain words
apiKeyAuthorizationBearer <token>Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.
id*stringRevoked (or already revoked).
application/json- response
id*stringclient*stringenvironment*string"sandbox""production"scopes*array<>label?stringcreated_at*stringdate-timerevoked_at?stringdate-timealso_revoked?array<string>Only in a revoke answer, the ids of the keys minted under this one that were revoked with it.
curl -X POST "https://example.com/keys/string/revoke" \ -H "Authorization: Bearer <your-api-key>"{ "id": "string", "client": "string", "environment": "sandbox", "scopes": [ "submit" ], "label": "string", "created_at": "2019-08-24T14:15:22Z", "revoked_at": "2019-08-24T14:15:22Z", "also_revoked": [ "string" ]}Mint an API key for a client; the key is shown once POST
The operator mints for any client. A client's admin key mints only for its own client and only scopes it holds. Only the SHA-256 is kept.
The stored files of a care-list invoice with their SHA-256 GET
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}.