invalid_api_key
- HTTP status
- 401 Unauthorized
What happened
The key is unknown, expired, revoked or retired, the person behind a personal key is no longer a member or no longer assigned any app the key covers, or your organisation's API access for it is not set up or no longer active.
What to do
Check that you send the whole key. A personal key is created in the hub's API area; for a new organisation integration key, contact komplai.
Example
JSON
{
"error": "invalid_api_key",
"request_id": "0f8e2c4a-6b1d-4e3f-9a7c-5d2b8e1f4a60",
"doc_url": "https://developers.komplai.dk/errors/invalid_api_key"
}Every response carries a Request-Id header, and an error body repeats it as request_id. Quote it when you ask komplai about a call.
Endpoints that can return it
- POST
/v1/redactPseudonymise a text - POST
/v1/redact/detectFind personal data in a text - POST
/v1/redact/restoreRestore the originals in a text - POST
/v1/redact/jobsSubmit a text job - GET
/v1/redact/jobs/{id}Read the status of a text job - DELETE
/v1/redact/jobs/{id}Delete a text job - GET
/v1/redact/jobs/{id}/resultRead the result of a text job - POST
/v1/redact/filePseudonymise the text of a PDF or Word file (beta) - POST
/v1/redact/file/jobsSubmit a PDF or Word file as a text job (beta) - GET
/v1/accessRead what this key can reach - GET
/v1/modelsList the permitted chat models - POST
/v1/chat/completionsCreate a chat completion - POST
/v1/decideEvaluate one text - POST
/v1/decide/batchEvaluate several texts - GET
/v1/coding/accountRead the coding account - GET
/v1/coding/modelsList the coding models - POST
/v1/coding/chat/completionsStream a coding completion