The symbols in a SYMBOL_LIST = items = RICs?
I'm a bit confused by the different terms:
- If i understood correctly, a "symbol list" contains a list of symbols. (This one is easy)
- A symbol and a RIC refer to the exact same thing. By example: EUR= is a RIC. It's also a symbol.
- A symbol/RIC is the identifier of an instrument.
Is that correct?
Best Answer
-
Yes, that's absolutely correct.
"Symbol" is a
generic term used to designate the name of an instrument. A “RIC” (Reuters
Instrument Code) is a type of symbol used by Thomson Reuters. ISIN, CUSIP and
SEDOLs are other types of symbols. Thomson Reuters services use
RICs to identify instruments. Services published by other provider applications
may use different symbol types.0
Answers
-
A "symbol list" is an unordered list of strings. To each symbol you can optionally attach a field list (rarely used feature).
Most often the strings in the list designate data item names on the same service as from which you obtained the symbol list itself. However, there are no formal requirements of what a symbol list contains. It is just a list of "something". Whoever created the feed will let you know what the strings in the list represents. I think this feature was given the name "symbol list" because it is sort of a generic term. 99% of the time you can think of a symbol list as a "data item name list".
Data item names on TREP and in TREP APIs are really convention agnostic. They do not at all have to follow the RIC naming standard. If you have a Thomson Reuters feed on your TREP then that one will use the RIC naming standard, but other feeds on your TREP may use a different standard. It is all up to the publisher. This is why the words "RIC" and "data item name" are not interchangeable.0 -
>> With TREP APIs you must use RICs to identify instruments.
Nope.
With TREP APIs you identify market data instruments by a so-called 'data item name'. This identifier is naming standard agnostic, it does not at all need to be a RIC.If you are consuming from a TR service (on your TREP), then yes, that specific service will most likely use the RIC standard.
0 -
You're
absolutely right. The last sentence of my answer ("With TREP APIs you must use RICs to identify instruments") is not correct. I should have said: "Thomson
Reuters services use RICs to identify instruments. Services published by other
provider applications may use different symbol types".Let me fix this to avoid any confusion.
Thanks for this clarification.
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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛