Skip to content

Commit e8ec31b

Browse files
authored
Merge pull request #2 from PatrickFarley/face-updates
Face updates
2 parents 82605c0 + 1c81a4e commit e8ec31b

File tree

1 file changed

+25
-22
lines changed

1 file changed

+25
-22
lines changed

articles/ai-services/computer-vision/concept-face-liveness-quick-link.md

Lines changed: 25 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -7,33 +7,32 @@ manager: nitinme
77

88
ms.service: azure-ai-vision
99
ms.subservice: azure-ai-face
10-
ms.custom:
1110
ms.topic: conceptual
1211
ms.date: 05/15/2025
1312
ms.author: pafarley
1413
feedback_help_link_url: https://learn.microsoft.com/answers/tags/156/azure-face
1514
---
1615

17-
# Face Liveness Quick Link (Preview)
16+
# Face Liveness quick link (Preview)
1817

1918
This article explains the concept of Face liveness quick link, its usage flow, and related concepts.
2019

2120
## Introduction
2221

23-
Azure Liveness Quick Link is an optional integration path for [Face liveness detection](concept-face-liveness-detection.md). It exchanges a liveness session’s session-authorization-token for a single use URL that hosts the capture experience on an Azure operated page. The service returns to a developer supplied callback endpoint after finishing the operation.
22+
Azure Face Liveness quick link is an optional integration path for [Face liveness detection](concept-face-liveness-detection.md). It exchanges a liveness session’s session-authorization-token for a single-use URL that hosts the face capture experience on an Azure-operated page. The service returns to a developer-supplied callback endpoint after finishing the operation.
2423

25-
Azure Liveness Quick Link provides multiple benefits to customers:
26-
- No need to embed the liveness client SDK. Easier integration in application side.
27-
- No need to keep track of liveness client SDK updates. Azure operated websites always use the latest and greatest version of liveness detection.
24+
Azure Liveness quick link provides multiple benefits to customers:
25+
- You don't need to embed the liveness client SDK. That allows for easier integration on the application side.
26+
- You don't need to keep track of liveness client SDK updates. Azure-operated websites always use the latest version of liveness detection.
2827

2928
## How it works
3029

31-
You can utilize the liveness quick link website liveness.face.azure.com to turn a liveness session into a shareable, single use link:
30+
You can use the liveness quick link website, `liveness.face.azure.com`, to turn a liveness session into a shareable, single use link:
3231

3332
:::image type="content" source="media/liveness/liveness-quick-link-diagram.png" alt-text="A diagram illustrates liveness quick link work flow":::
3433

35-
1. Start a session server side. Your backend asks Face API for a new liveness session and receives a short lived authorization token that represents that session.
36-
2. Swap the token for a link. Your backend sends the token to the Quick Link service, which creates a one time URL tied to the session. here are examples to post request:
34+
1. Start a session with your server-side code. Your application backend requests a new liveness session from the Face API and receives a short-lived authorization token that represents that session.
35+
2. Swap the session token for a link. Your application backend sends the token to the quick link service, which creates a one-time URL connected to the session. Here are examples of the post request:
3736

3837
#### [C#](#tab/csharp)
3938
```csharp
@@ -113,16 +112,20 @@ You can utilize the liveness quick link website liveness.face.azure.com to turn
113112
curl --request POST \
114113
--url https://liveness.face.azure.com/api/s \
115114
--header 'authorization: Bearer <session-authorization-token>'
116-
```
117-
118-
An example response:
119-
```json
120-
{
121-
"url": "/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f"
122-
}
123-
```
124-
Compose the returned url after liveness quick link web site `https://liveness.face.azure.com/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f`
125-
126-
3. Send the link to the user. You can redirect the browser, show a button, or display a QR code—anything that gets the user to open the link on a camera enabled device.
127-
4. Azure hosts the capture. When the link opens, the Azure operated page guides the user through the liveness check sequence using the latest Liveness Web Client.
128-
5. Get the outcome callback. As soon as the check finishes—or if the user abandons or times out—Quick Link notify to your callback endpoint so your application can decide what happens next.
115+
```
116+
117+
---
118+
119+
The following is an example response:
120+
121+
```json
122+
{
123+
"url": "/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f"
124+
}
125+
```
126+
127+
Use that value to construct the liveness quick link web page: `https://liveness.face.azure.com/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f`
128+
129+
1. Send the link to the user. You can redirect the browser, show a button, or display a QR code—anything that lets the user open the link on a camera-enabled device.
130+
1. Azure hosts the capture experience. When the link opens, the Azure-operated page guides the user through the liveness check sequence using the latest Liveness web client.
131+
1. Get the outcome callback. As soon as the check finishes—or if the user abandons or times out—the quick link service notifies your callback endpoint so your application can decide what happens next.

0 commit comments

Comments
 (0)