POST /api/v1/users/{userId}/factors/{factorId}/resend
Resends an sms, call, or email factor challenge as part of an enrollment flow
For call and sms factors, Okta enforces a rate limit of one OTP challenge per device every 30 seconds. You can configure your sms and call factors to use a third-party telephony provider. See the Telephony inline hook reference. Okta round-robins between SMS providers with every resend request to help ensure delivery of an SMS and Call OTPs across different carriers.
Note: Resend operations aren't allowed after a factor exceeds the activation rate limit. See Activate a Factor.
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
userId |
String | Yes |
ID of an existing Okta user |
factorId |
String | Yes |
ID of an existing user Factor |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
templateId |
String | No |
ID of an existing custom SMS template. See the SMS Templates API. This parameter is only used by |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
factorType |
String | No |
Type of the Factor Possible values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.