curl --request POST \
--url https://api.mnemom.ai/v1/api-keys/{key_id}/rotate \
--header 'Authorization: Bearer <token>'{
"key_id": "<string>",
"key": "<string>",
"key_prefix": "<string>",
"name": "<string>",
"scopes": [
"<string>"
],
"rotated_from": "<string>",
"old_key_revoked_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}Atomically mints a replacement key with the same name and scopes as the original, then immediately revokes the old key. The full new secret is returned in the response — this is your only chance to capture it. Old key is invalid as soon as the response is returned; if you need overlap with an in-flight deploy, create a second key first via POST /api-keys, ship your code, then DELETE the old key. Rotation is for the suspect/compromised-key case where overlap is the opposite of what you want.
curl --request POST \
--url https://api.mnemom.ai/v1/api-keys/{key_id}/rotate \
--header 'Authorization: Bearer <token>'{
"key_id": "<string>",
"key": "<string>",
"key_prefix": "<string>",
"name": "<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