Endpoints
Perform a retry
POST
/
retry
This endpoint is not required anymore.
Retries are now handled automatically for all apps created after 2024-05-22. You can still use this endpoint if you prefer to have more control over user retries.
How automatic retries work
Automatic retries use the Stateless Mode. It systematically re-uses an existing authentication flow if one is found and is not expired.
Stateless mode
Authorizations
x-api-key
string
headerrequiredBody
application/json
customer_uuid
string
requiredYour customer UUID, which can be found in the API settings in the dashboard.
authentication_uuid
string
requiredThe authentication UUID that was returned when you created the authentication.
Response
200 - application/json
authentication_uuid
string
The UUID of the corresponding authentication.
status
enum<string>
The status of the retry. Possible values are:
approved
- The retry was approved and a new code was sent.denied
- The retry was denied.no_attempt
- No attempt was sent yet, so a retry cannot be completed.rate_limited
- The authentication was rate limited and cannot be retried.expired_auth
- The authentication has expired and cannot be retried.already_validated
- The authentication has already been validated.
Available options:
approved
, denied
, no_attempt
, rate_limited
, expired_auth
, already_validated
created_at
string
next_retry_at
string
The time at which the next retry will be available.
remaining_retry
integer
The number of remaining retries.
Was this page helpful?