Complete a 2FA reset after liveness passes
Step 3 — call once /user/2fa/reset/status reports LIVENESS_PASSED. The behaviour depends on the factor the reset was opened for: — totp: any existing TOTP configuration is cleared and a fresh secret and provisioning URI are returned; finish enrollment via /user/resume/setup-two-factor, which marks the reset COMPLETED. — passkey: if the reset was opened with a credentialId, that passkey alone is removed, the reset is closed in this call and fresh PublicKeyCredentialCreationOptions are returned so a replacement can be enrolled via /user/passkey/register/complete if wanted (removedCredentialId echoes the id); otherwise every passkey is removed, the options are returned, and the registration via /user/passkey/register/complete closes the reset. — sms: provide the new mobile (countryCode + number); the stored number is updated and the reset is closed in this one call (no additional one-time code is required, as the identity verification check serves as proof of identity). — Completing the reset revokes the user's active SCA sessions and clears any time-bounded lock.
Request
- Base URLhttps://www.sandbox.striga.com/api/v1
- URLhttps://www.sandbox.striga.com/api/v1/user/2fa/reset/complete
- AuthAPI key in header api-key and API key in header Authorization
Request body
Response
Reset advanced. The shape depends on the factor (factor discriminates): totp returns a fresh secret + provisioning URI to enroll via /user/resume/setup-two-factor; passkey returns WebAuthn creation options to enroll via /user/passkey/register/complete (plus removedCredentialId when the reset was opened for one credential; the reset is then already terminal); sms returns ok: true (reset is already terminal).
Changes
No recorded changes to this operation across all 1 revision of this API.