API Web Page access and Tick History CFS Tuturial
Questions from client:
- Access to the API webpage (e.g. https://apidocs.refinitiv.com/Apps/ApiDocs) via browser always gets blocked (403). Is it expected?
- As I am trying to follow the CFS tutorial (https://developers.refinitiv.com/en/article-catalog/article/introduction-to-client-file-store--cfs----python#Token), the sample code snippet includes constants:
- TOKEN_FILE & SCOPE, could I know how to get it?
- CLIENT_ID & CLIENT_SECRET. How to get them as well? I am aware that there is an `App Key` on https://amers1-apps.platform.refinitiv.com/apps/appkeygenerator
And just to confirm that TOKEN_ENDPOINT is https://api.refinitive.com/auth/v1/token
Best Answer
-
Thanks for reaching out to us.
The client must have the Refinitiv Data Platform credential to access that API docs.
The endpoint to get the token is https://api.refinitiv.com/auth/oauth2/v1/token.
Please refer to the Authorization - All about tokens tutorial for more information regarding RDP tokens.
Moreover, you need to verify if the client's account is the RDP's Version 1 Authentication or RDP's Version 2 Authentication. For more information, please refer to the Getting Started with Version 2 Authentication for Refinitiv Real-Time: Overview article.
I hope that this information is of help.
0
Answers
-
Hello @daniel.zuliani
About the second question, the Python CFS article source code sends an authentication request to RDP and saves the RDP tokens to a file variable named TOKEN_FILE. You can get the complete application source code from the GitHub repository.
That logic is based on the RDP APIs Quickstart and Python tutorials source code, Python starter examples, you can download the examples from the RDP APIs download page. The RDP APIs Tutorial - Authorization in Python is also a good place to get started.
The CLIENT_SECRET is not being used in the RDP Version 1 authentication, you can just send a blank value to it.
CLIENT_SECRET = ""
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛