Skip to main content
This is the standard use case delivered by the Send Verification Process. An authenticated user selects to send a verification message to either an e-mail address or phone number, as they may have misplaced or accidentally deleted the previous one. The email/mobile is registered to this user, but it still has an activating or pending status.

​
Request

Your client calls the Process Start API to initialize the Process. Unlike most Process Start-based Processes, Send Verification requires the client to provide the target authN ID upfront in the initial request.
Note: In this example use case, the client provides the authN ID in the API request URL. However, the client can specify the authN ID in the request body.

​
Response

If the target authN ID is valid, then Digital Identity Management issues a new action token, and sends it (either as a clickable link, an OTP, or both) to the target email address or mobile number. The Process then returns an HTTP 200 status:
OTP Verification & Resend Verification Any Process that sends a Digital Identity Management action token to a user also returns a corresponding Proof key for Action Token (PKAT) to the client application. In order to enable OTP verification on the UI, the client must retain the PKAT returned in the final Process response. The PKAT, along with the user-supplied OTP, is required for the Session Token API to invoke the subsequent Process to complete the user journey. In cases where the user is anonymous, the PKAT is required if the application wants to provide a quick token resend option on the UI, using the Token Resend API. This method applies to cases where the user is anonymous (i.e., they are not authenticated in Digital Identity Management). However, if the user is currently authenticated in Digital Identity Management, the client application can instead invoke the Send Verification Process for this purpose.