Cancel account deletion
DELETE /fapi/v1/me/deletion · called from the environment's sign-in host
Cancels the signed-in user's own pending account deletion during the waiting period; the account becomes active again. Only a deletion the user started can be cancelled here: a deletion started by an administrator, a bulk job or SCIM, or one whose waiting period has ended, answers 409 conflict. No body and no recent sign-in are needed.
Request
Headers:
| Header | Required | Description |
|---|---|---|
Idp-Client |
yes | SDK identifier. |
Origin |
yes | Must be exactly https://<sign-in host>. |
Response
204 No Content.
Errors
| Status | Code | When |
|---|---|---|
| 401 | unauthenticated |
No valid session cookie. |
| 403 | origin_not_allowed |
Origin is missing or wrong. |
| 404 | not_found |
The account is not being deleted. |
| 409 | conflict |
The deletion cannot be cancelled by the user. |
| 503 | service_unavailable |
The user directory is temporarily unavailable; retry after Retry-After. |
Example
curl -X DELETE https://example.keenauth.app/fapi/v1/me/deletion \
-H "Idp-Client: my-app/1.0.0 (node/22.0.0)" \
-H "Origin: https://example.keenauth.app" \
-b cookies.txt
Personal data
This endpoint carries personal data: end-user profile. Personal data in the KeenAuth APIs describes what is stored, how long it is kept and how it is deleted. Do not send special categories of personal data (health, biometric data, religion, political opinions, sexual orientation) in any field.