Confirm passkey deletion — step 2 of 2

Verifies the assertion against the challenge issued by /user/passkey/delete and removes the credential that challenge was bound to. The assertion must be made by that very passkey: an assertion by any other passkey, even one enrolled on the same account, is refused with 999998 before it is verified. — One challenge authorises one deletion: confirming an already-consumed challenge is rejected with 999998; an unknown or expired challengeId with 999995; an assertion that does not verify with 999998. The attempt cap is the same as for transaction challenges. The assertion request is single-use: if the assertion was accepted but the removal failed downstream, the challenge is handed back and the deletion is started again from /user/passkey/delete.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
string
required

From /user/passkey/delete.

string
required

Client IP address, recorded with the verification event for audit purposes.

string
required

The origin the assertion was made at (the browser origin, or the app origin for native apps).

credential
object
required

WebAuthn PublicKeyCredential assertion from navigator.credentials.get(), made by the passkey being deleted.

Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json