api_key_expired
- HTTP status
- 401
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- Yes
API key expired. The key reached its expiry date, or its rotation grace period ended after it was replaced.
What it means
The API returns HTTP 401 with error.code set to api_key_expired. The default message is: "This API key has expired."
Common causes
- The expiry chosen when the key was created has passed.
- The key was rotated and the grace period is over.
How to identify it
Check the response status (401) and error.code (api_key_expired). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.
How to fix it
- Switch to the replacement key, or ask a workspace admin to create a new key in the console.
Retry guidance
Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
Nothing was done and nothing was stored (under an Idempotency-Key, if you sent one), so the request can be sent again, with the same key if you used one, once the cause is fixed.
Who can fix it
A workspace administrator usually has to act, in the RelationsAI console.
When to contact support
If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).
Example error response
JSON
See all codes in the error-code reference.