Exchange codes (TRTHv1) / DSS source field
Hi, we have found out that the exchange codes in TRTHv1 are not always matching the DSS field called 'source'. Is there an overview or mapping available we can use to migrate TRTHv1 exchange codes to DSS source fields? We really need this to migrate settings at our customers. Many thanks in advance!
Best Answer
-
Hi all
I have responded to Philipp with the below details -
I confirm
“GetHistoricalExchanges” and “GetHistoricalCurrencies” are the right methods to
obtain the numerical-alphabetical translations of exchange codes and currency
codes.The direct method of obtaining
the exchange codes and currency codes is making a “Reference Data –
Historical Reference” request (see highlighted
below extracts from the API guide - http://paz.thomsonreuters.com/portalfiles/11047/ThomsonReutersTickHistory10.8RESTAPIUserGuidev1.1(2017121).pdf)There’s a working example of a
request for Historical Reference data included in the hyperlink in the
highlighted area.With respect Source Codes in
DSS, the complete list is documented here - https://customers.reuters.com/a/productsupport/Datascope/GCODES/price_src_cds.htmlAnd the list of exchange codes
are documented here - https://customers.reuters.com/a/productsupport/Datascope/GCODES/dse_exch_cds.htmlSource codes in DSS and the
exchange codes are not necessarily the same. For certain exchanges, it is the
RIC suffix that is used in DSS as source code. E.g. for NASDAQ, .OQ is the DSS
source code whereas the exchange codes are NAS, NSM, NMS. For certain
exchanges, e.g. National Stock Exchange of India (NSI), the source codes and
the exchange codes are the same i.e. NSI. For non-exchange traded instruments
you will have Source codes but no exchange codes. In short, there’s no
established link between DSS source codes and TR Exchange codes.1
Answers
-
Hi Philipp: would you be able to provide some examples highlighting differences in the TRTH v1 exchange codes vs DSS "source" field?
0 -
For example for RIC 'XS1017615920=TX'
The TRTHv1 exchange code is 'ETX'.
But in the DSS request the source is 'TLX'.
Since we are seraching for RICs using the exchange code this is causing some trouble with existing configurations. In the rollout we need to migrate TRTHv1 exchange codes to DSS source codes. Therefore a mapping between this two fields is what we really need.
Thanks in advance!
0 -
While I am looking into this I find "Exchange:
ETX" in the DSS Historical search screen results for RIC XS1017615920=TX and so I am not exactly sure where you found "TLX".Can you help me know what kind of DSS request you made that returned that to you? Was it a REST API call? If so, do you have the posted request data you can provide?
0 -
Here is one example of Search/GovCorpSearch
{"SearchRequest":{"AssetStatuses":["CLD","CAN","DFS","RDM","EXC","MAT","FNG","DEF","ISS","LIQ","NAC","PRE","PUT","RPN","REF","RMK","RBM","FDD","REP","RES","TEN","TBC","TBE","TBI","TBP","TBR","TBB","WHN"],"CurrencyCodes":["EUR"],"Group":{"Agency":true,"Government":true,"Corporate":true,"Supra":true},"Identifier":"XS1017615920","IdentifierType":"Isin","PreferredIdentifierType":"Ric"}}
I have also attached a screenshot of TRTHv1 showing the RIC we are interested in.
In TRTHv1 the exchange code is ETX and in the DSS response the source field is "TLX".
0 -
Sorry, the comment limit was reached.
What we need is a mapping of TRTH exchange codes to DSS source codes.
Thx in advance!
0 -
Hi Philipp
With respect Source Codes in
DSS, the complete list is documented here - https://customers.reuters.com/a/productsupport/Datascope/GCODES/price_src_cds.htmlAnd the list of exchange codes
are documented here - https://customers.reuters.com/a/productsupport/Datascope/GCODES/dse_exch_cds.htmlSource codes in DSS and the
exchange codes are not necessarily the same. For certain exchanges, it is the
RIC suffix that is used in DSS as source code. E.g. for NASDAQ, .OQ is the DSS
source code whereas the exchange codes are NAS, NSM, NMS. For certain
exchanges, e.g. National Stock Exchange of India (NSI), the source codes and
the exchange codes are the same i.e. NSI. For non-exchange traded instruments
you will have Source codes but no exchange codes. In short, there’s no
established link between DSS source codes and TR Exchange codes.1 -
Thanks a lot for that information. Still this causes some trouble on our side.
One last question regarding this topic. We now know that the source field is something different. But, what is the reason why in TRTH we sometimes see an exchange code assigned to a RIC and in DSS/TRTHv2 we just see a different one in the exchange code field?
Screenshot attached.
0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛