curl --request POST \
--url https://api.mnemom.ai/v1/orgs/{org_id}/api-keys/{key_id}/rotate \
--header 'Authorization: Bearer <token>'{
"key_id": "<string>",
"key": "<string>",
"key_prefix": "<string>",
"name": "<string>",
"org_id": "<string>",
"scopes": [
"<string>"
],
"rotated_from": "<string>",
"old_key_revoked_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}Atomic mint-new + immediately-revoke-old, with the same name and scopes as the original. The full new secret is returned only in this response. No grace period — old key is invalid immediately. If you need overlap with an in-flight deploy, create a second key first via POST /orgs/{org_id}/api-keys, ship, then DELETE the old key. Owners and admins may rotate any org key; members may rotate keys they created.
curl --request POST \
--url https://api.mnemom.ai/v1/orgs/{org_id}/api-keys/{key_id}/rotate \
--header 'Authorization: Bearer <token>'{
"key_id": "<string>",
"key": "<string>",
"key_prefix": "<string>",
"name": "<string>",
"org_id": "<string>",
"scopes": [
"<string>"
],
"rotated_from": "<string>",
"old_key_revoked_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}Supabase JWT token in Authorization: Bearer header
Organization identifier (e.g. org-abc12345)