Intereaction with API Playground Beta Endpoints

Hi,
I am looking to experiment with the API endpoints located in the API Playground, specifically the ones related to messenger/chat. I see that there are examples for how to utilize the messenger/beta1 endpoints. I have obtained an API Key from App Key Generator, but am not sure how to use this key to login/authenticate myself and interact with the api endpoints. Can you provide some starter instructions on how to do this?
Thanks!
Answers
-
Hello @refinitiveuser123,
A user needs entitlements to use a specific products (API endpoints). You can speak with your LSEG account manager to get access to these services.
After that you can try the working API sample on the GitHub repo. Typically, Beta endpoints are not available for general use.
0 -
Hi Gurprett,
Thanks for the fast response. I thought the github repo was outdated because the normal Messenger API is no longer supported?
Thanks!
0 -
The example code in the linked Repo uses the RDP Beta1 endpoint.
0 -
Which also seems to be deprecated according to this answer -
Please reach out to the account manager to check the current status of Messenger API.
0 -
I believe that Messenger 2.0 API is coming out soon. Is this /beta1 not applicable to that? All I am looking for is to receive messages, but none of the LSEG technical team I have asked via Helpdesk seem to have a clear answer.
0 -
Hello @refinitiveuser123
I spoke with the product team and have been informed that new version of Messenger API has not yet been released. These Beta 2 endpoints are not the new version.
0 -
Thanks Gurpreet. So does that mean the /beta1 endpoints in the API playground are not usable anymore? Since Messenger 1.0 is obsolte and Messenger 2.0 does not use these?
How do people currently trading through Refinitiv Messenger extract the chat logs for compliance purposes?
0 -
You can continue to use /beta1 endpoint if it was already working for you. For new users, they should wait for the release of the version 2.0 (which I have been informed will happen soon).
1
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
- 615 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
- 249 ETA
- 554 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
- 643 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛