Synchronous and Asynchronous Implementation

There are two approaches to implementing Silent Authentication: synchronous and asynchronous. Each approach has its own pros and cons. However, we recommend using the asynchronous method. For details about the synchronous approach, refer to this guide.

Asynchronous Implementation

An asynchronous implementation is very similar to the synchronous method; instead of using the device client to make a series of calls, every part of the workflow is included in webhook callbacks sent to a URL you define.

This guide explains how to implement silent authentication using the asynchronous approach, where your backend sets up a callback to receive the authentication result.

VonageApp BackendMobile AppVonageApp BackendMobile AppTrigger VerificationOpen check_url over cellular network using Vonage SDKCheck Verification CodeVerify phone numberPOST v2/verifyWebhook 202 OK (check_url, request_id) / ErrorResponse (check_url)GET check_urlSeveral 302 RedirectsHTTP 200 (request_id, code)Request (request_id, code)POST v2/verify/:request_id (code)HTTP 200 (status: completed)Response (Completed)

For a detailed, step-by-step explanation of this flow, including request handling, callbacks, and error scenarios, see the Asynchronous Implementation How-To guide.

Webhooks

In asynchronous implementation, every part of the workflow is included in webhook callbacks sent to a URL you define.

Webhooks are an extension of an API - instead of your code requesting data from our API platform, Vonage sends the data to you via a web request to your application. The Verify API webhook receives status updates on your requests, and will be the result of an earlier API call - this type of webhook is also called a "callback".

To read more, refer to this guide.