The REST API seems to support basic authentication and authentication via Token for test users. I...
Best Answer
-
Hi Josef,
The intention of a Token is for efficiency / re-use.
Aim for DSS users should be to poll the Authentication/RequestToken endpoint once (or a few a times as possible) using DSS (Basic) credentials to retrieve the Token "value", then re-use that Token in any DSS requests going forward for as long as the Token is valid.
I believe a Token is valid for 24 hours.
The concept of test users does not apply relating to this question.
Best regards,
Gareth
0
Answers
-
I confirm: a token is valid 24 hours.
0 -
Page 8 "Reuse Authentication Tokens for Faster Authentication" in Best Practices (for DataScope Select) (Developer Community access required) should help here.
Sourced from: https://hosted.datascopeapi.reuters.com/RestApi.Help/Home/Index (DSS access required)
0 -
Thank you for the answer. I understand the concept of the session token. But my scenario would make just one API Request once a day. If I can call the API directly with basic authentication without getting the token first, this would considerably reduce the implementation effort on the middleware that is making the API call. So I want to make sure: Is basic authentication supported for REST API requests?
0 -
Hi Josef,
Given you've mentioned that your scenario would make just one API Request once a day, then my view is that you should be able to use the Basic within the 1 request per day. In the 1 step workflow example you've mentioned adding the Authentication/RequestToken call first adds an unrequired step. If you find that your DSS workflow does requires more than the one request to DSS only then does it become best to retrieve the Token within a daily workflow.
Best regards,
Gareth
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛
