@@ -286,7 +286,7 @@ The high-level steps involved in liveness orchestration are illustrated below:
286
286
print (f " Session status: {liveness_result.status}" )
287
287
print (f " Liveness detection request id: {liveness_result.result.request_id}" )
288
288
print (f " Liveness detection received datetime: {liveness_result.result.received_date_time}" )
289
- print (f " Liveness detection result : {liveness_result.result.response.body.liveness_decision}" )
289
+ print (f " Liveness detection decision : {liveness_result.result.response.body.liveness_decision}" )
290
290
print (f " Session created datetime: {liveness_result.created_date_time}" )
291
291
print (f " Auth token TTL (seconds): {liveness_result.auth_token_time_to_live_in_seconds}" )
292
292
print (f " Session expired: {liveness_result.session_expired}" )
@@ -549,8 +549,6 @@ The high-level steps involved in liveness with verification orchestration are il
549
549
name : 'Parameters' ,
550
550
body : {
551
551
livenessOperationMode : 'Passive' ,
552
- sendResultsToClient : false ,
553
- authTokenTimeToLiveInSeconds : 60 ,
554
552
deviceCorrelationId : '723d6d03-ef33-40a8-9682-23a1feb7bccd' ,
555
553
},
556
554
},
@@ -566,7 +564,7 @@ The high-level steps involved in liveness with verification orchestration are il
566
564
console .log (`Auth token : ${createLivenessSessionResponse .body .authToken }`);
567
565
console .log ('The reference image:' );
568
566
console .log (` Face rectangle : ${createLivenessSessionResponse .body .verifyImage .faceRectangle }`);
569
- console .log (` The quality for recognition : ${createLivenessSessionResponse .body .verifyImage .qualityForRecognition })
567
+ console .log (` The quality for recognition : ${createLivenessSessionResponse .body .verifyImage .qualityForRecognition }` )
570
568
```
571
569
572
570
#### [REST API (Windows)](#tab/cmd)
0 commit comments