Websocket endpoints standard vs premium configuation

Hi
I have question on how to identify the "Standard vs Premium Connection" configuration.
Discovery service just returns with location array with either us-east-1a mapped to amer1 endpoint or us-east-1b mapped to amer2 endpoint.
OR location array with multiple entries (both 1a and 1b mapped to amer3 endpoint).
Based on documentation I think amer3 is standard configuration and in our application we would like to go with this type of configuration.
How do we identify amer3 is standard configuration? there is no attribute in response that tells us this info.
{
"port":443,
"location":[
"us-east-1a",
"us-east-1b"
],
"provider":"aws",
"transport":"websocket",
"endpoint":"amer-3.pricing.streaming.edp.thomsonreuters.com",
"dataFormat":[
"tr_json2"
]
},
{
"port":443,
"location":[
"us-east-1a"
],
"provider":"aws",
"transport":"websocket",
"endpoint":"amer-1.pricing.streaming.edp.thomsonreuters.com",
"dataFormat":[
"tr_json2"
]
},
{
"port":443,
"location":[
"us-east-1b"
],
"provider":"aws",
"transport":"websocket",
"endpoint":"amer-2.pricing.streaming.edp.thomsonreuters.com",
"dataFormat":[
"tr_json2"
]
}
Best Answer
-
Hello @krishna muppavarapu
I have found the table below in page 22 of ERT_Cloud_20.pdf . I am not sure if this what you are looking for:
For more details, please refer to ERT_Cloud_20.pdf
You may contact Elektron Real Time in Cloud support team via MyRefinitiv to confirm standard vs premium configuration.
0
Answers
-
By looking at the table I can tell "Standard" configuration for US is mapped to amer3 endpoint...But how do I programmatically find that...Should we just look at if end point mapped to more than one location then it is standard configuration?
0 -
Hello @krishna muppavarapu
Sorry. I do not know how to find "Standard" configuration programmatically. Please contact Elektron Real Time in Cloud support team via MyRefinitiv . The team should be able to help you on this.
0 -
Hello @krishna muppavarapu,
I don't believe there is a difference between ERT websocket pricing endpoints that are discernible to a connecting Elektron Websocket consumer application.
If you are using discovery mechanism, you will be pointed to your regional endpoint which is most available at the time of the discovery request, which will provide you with standard service.
I am not sure, but guessing that you may be thinking of other Premium services, not ERT.
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
- 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 中文论坛