Skip to content

Verification workflow

The following is an example of how a two-factor authentication process would be implemented using VerifyAPI. The workflow looks something like this:

VerifyAPI workflowVerifyAPI workflow

Step 1 - User supplies destination

In a typical scenario, the user would supply a destination number to be verified. This could be a telephone, mobile number, or any other destination that can receive a verification code.

In a two-factor authentication scenario, the phone number of this user is likely to already be known by the web site or app, and the user would not need to supply it.

Step 2 - Verification is requested

Your web site or app would then send a request to VerifyAPI to initiate the verification process. This request would include the destination number and the channel to be used for delivery.

Step 3 - Verification code is delivered

VerifyAPI generates a numeric, alphanumeric or alphabet code depending on your channel configuration and sends it to the destination.

Step 4 - User supplies verification code

The user will receive the code and enter it into your web site or app.

Step 5 - Verification is confirmed

The code supplied in step 4 is used to call our /confirm endpoint in conjunction with the request id returned in step 2. If the code is correct, the verification is confirmed and the user is authenticated.

For more information, check out our Quickstart tutorial.