Are there any usage restrictions about liveness token?

I am using the liveness token api, /verification/v1/liveness/token,
our app will use this token to call the liveness SDK.
I want to know if different users and devices can use the same token?
Best Answer
-
Hi infiyang,
Thank you for reaching out to us!
Considering your service maintain only one token at all times, you can make use of the same liveness token for different cellphone.
Best regards,
Virgill
0
Answers
-
Thank you for reaching out to us!
Kindly note that the Liveness Token Request API endpoint which generates the token(s) (https://api.refinitiv.com/verification/v1/liveness/token) cannot be shared across different users and devices. The token for this end point does expire as it uses the OAUTH 2.0 GrantType: "client_credentials" technology.
Furthermore, the Liveness Token Request API endpoint token is preceded by the Get Access Token API endpoint which offers you an intitial access_token. Thereafter you make use of the Liveness Token Request API endpoint which will offer you the said token, valid for 60 minutes. In between there is the Get Access Token using Refresh Token API endpoint which can be used to request a new token (refresh token) for Liveness Token Request. Both the Get Access Token and Get Access Token using Refresh Token are located in the directory Authentication of the rdp_postman_collection.
You can explore the possibility of sharing single access credentials amongst various devices who will then receive their own tokens. However, user discretion is advised here.
Please feel free to reach out if you have any further questions.
Best regards,
Virgill
0 -
Thanks Virgill for your reply.
But I test the condition with different cellphones in our mobile app,both cellphones use the same liveness token to call the liveness SDK, and both cellphones take liveness photo successfully. So does this means it is ok to use the same liveness token for different cellphone?
Our mobile app get the liveness token from our service, and the service maintain only one valid liveness token all the time.
PS, we just use the facecapture, no other liveness features.
0 -
Thanks for solving my doubt.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 614 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 639 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛