Recover User
Recover User
Recovers a user, using a recovery credential. After successfully recovering the user, all of the user’s previous credentials and personal access tokens will be invalidated.
This flow requires cryptographic validation of newly created credential(s) using a recovery credential. The recovery.credentialAssertion.clientData field’s challenge must be the base64url-encoded representation of the newCredential object.
The process is as follows:
- Construct the
newCredentialobject, using the challenge obtained from either the Create Recovery Challenge or Create Delegated Recovery Challenge endpoints. - Serialize the
newCredentialobject to JSON and then base64url-encode the resulting JSON string. This base64url-encoded string will serve as the challenge for therecovery.credentialAssertionobject. - Construct the
recovery.credentialAssertionobject, using the base64url-encoded string generated in step 2 as its challenge.
POST
Recover User
Documentation Index
Fetch the complete documentation index at: https://docs.dfns.co/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
❌ Organization User (CustomerEmployee)❌ Delegated User (
EndUser)❌ Service Account
✅ Recovery Code
Required Permissions
No permission required.Authorizations
Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
Last modified on May 29, 2026
