This command allows you to request a single Secure Pin authentication.
The server will respond with a unique identifier for each 2FA request (referred to as an API request ID). This API request ID can be used to track and monitor the status of your 2FA request.
Note: the REST API may respond with various HTTP status codes.
Secure Pin challenge flow
- Step 1: Make an
HTTPPOST to have a
PINcode sent to a mobile number. You can specify various optional parameters within your request. An API request ID will be returned.
- Step 2: Use the resulting request ID to validate the
PINyour client has received and entered on the website by making a PUT call to the REST API. To do this, append the request ID received for that request to the API URL and then pass the
PINcode within your request.
- Step 3: As a response (
GET), you will receive a data packet with the status of the challenge (challengeSolved) set to either true or false, as well as a description of the status.
Make a new multi-factor authentication (MFA) request. A message is sent with the challenge to the user (such as a
PIN code or a URL to a grid of images).
|from||no||For sending from a two-way number or specifying a custom sender ID|
Only accepts pin or grid
|customPin||no||Alphanumeric. Minimum length: 4 characters; maximum length: 8 characters|
|overrideExpireTime||no||Defaults to 5 minutes|
|maximumRetries||no||Defaults to 1 attempt|
- API Request ID (to reference the MFA)
- Only one mobile number can be specified per
- The from parameter represents the two-way number that you are sending from. This parameter is only required if you want to send messages using a two-way number (short code or long number).
- The maximumRetries parameter indicates how many times a
PINcode may be guessed.
- The customPin parameter can be used to specify a custom PIN code instead of using the system-generated PIN code.