Request step-up scope
Initiate a step-up authentication flow for the given scope.
Two reserved scopes (prld:phone:register, prld:email:register)
drive the preformatted “register identifier” flow without consulting
the customer’s delegation hook. The identifier value must be supplied
on metadata.identifier.
Body
A scope identifier. Two reserved scopes drive the preformatted
register-identifier flow:
prld:phone:register (adds a phone number, OTP step verify_sms)
and prld:email:register (adds an email address, OTP step
verify_email). Register scopes require metadata.identifier
and must be listed in the app's step-up allowed_scopes to be
usable.
^[a-zA-Z0-9.\-_:]+$"transfer:write"
Response
OK
WebAuthn PublicKeyCredentialRequestOptions in the WebAuthn Level 3
JSON form (binary fields are base64url-encoded). Present only when the
step-up step the response advanced to is verify_passkey; pass it to
navigator.credentials.get({ publicKey }). The frontend SDKs cache it
keyed on the challenge id and run the assertion automatically.