Skip to main content
The API object for the password-reset-post-challenge Actions trigger exposes methods for controlling access, requesting MFA challenges, configuring redirects, rendering prompts, managing the transaction, and caching data.

api.access

Modify the access of the user that is attempting to reset their password.
void
Mark the current password reset attempt as denied. This will prevent the end-user from completing the password reset flow. The flow will immediately stop following the completion of this action and no further Actions will be executed.
Example
Parameters

api.authentication

Request changes to the authentication state of the current user’s session.
void
Request a challenge for multifactor authentication using the supplied factor. The challenge is shown if the user has not already satisfied the requirements.
Example
Parameters
void
Request a challenge for MFA using any of the supplied factors, showing a factor selection screen first.
Example
Parameters

api.redirect

Configure and initiate external redirects.
string
Create a signed session token suitable for use as a query string parameter in a redirect. The target endpoint verifies authenticity using a shared secret.
Example
Parameters
void
Trigger a browser redirect to the target URL immediately after this action completes.
Example
Parameters
object
Retrieve and verify data encoded in a JWT token passed to the /continue endpoint.
Example
Parameters

api.prompt

Render a custom prompt screen.
void
Render a custom prompt during the flow.
Example
Parameters

api.transaction

Configure the transaction.
void
Set the URL that the user should be redirected to after the password reset.
Example
Parameters

api.cache

Store and retrieve data that persists across executions.
void
Delete a cached record at the supplied key if it exists.
Example
Parameters
object | undefined
Retrieve a cached record at the supplied key. If found, access the value via record.value.
Example
Parameters
void
Store or update a string value in the cache at the specified key. Values are scoped to the Trigger and subject to the Actions Cache Limits. If no lifetime is specified, a default lifetime of 15 minutes will be used.Important: This cache is designed for short-lived, ephemeral data. Items may not be available in later transactions even if they are within their supplied lifetime.
Example
Parameters