company vs. security question

Hello.
I am collecting data using this very simply piece of code:
response = ld.get_history( start = min_date, universe= security, end = max_date, fields= price_fields, adjustments = adjustment_factor, )
I am using RICs as identifiers. How do I make sure that I am only collecting price data for the primary security? Is there a way to use screen to do that?
Cordially,
Joao Quariguasi
Answers
-
Thank you for reaching out to us.
Typically, when using RICs, the API returns historical data associated with them.
Could you please provide more details about your question? Including specific examples would be especially helpful.
0 -
Hello. In the example above, this is my list of rics,
ASOS.L
FTCHQ.PK
ZALG.DE
RKET.H
CNV.PA
DUST.ST
"
MATP.PA^B23"
BHGF.ST
ZO1G.HSay the data I am collecting, fields = 'OFF_CLOSE''. How do I know from which security is this data being downloaded, given that one company can have more than one security. Are RICs security specific, or company specific?
0 -
Each RIC can provide different sets of historical fields.
You may use the TR.xxx fields instead (such as TR.PriceClose) with the ld.get_data method.
RICS = ['ASOS.L', 'FTCHQ.PK', 'ZALG.DE','RKET.H','CNV.PA','DUST.ST','MATP.PA^B23','BHGF.ST','ZO1G.H'] ld.get_data( universe = RICS, fields = ['TR.PriceClose.Date','TR.PriceClose'], parameters = {'SDate':'2025-06-01', 'EDate':'2025-06-13'} )
You can use the Data Item Browser tool to search for the available fields and parameters.
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
- 687 Datastream
- 1.4K DSS
- 621 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
- 254 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 669 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 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
- 48 中文论坛