=FINR Not being Returned

On DSS when I search for RIC for the ISIN US207932AB01 it retunes the two instruments below, both instruments have the same ISIN but different identifiers.
When I try and run a historical request via the DSS REST API using the ISIN 'US207932AB01' it only returns the instrument on the EJV source and not both, which I thought it would have, If I run a similar request for the ISIN 'GB00BH4HKS39'; I get several records returned on various sources.
Without being able to get the RIC from the ISIN we can't get the Time and Sales data.
Best Answer
-
Typically, the TickHistoryTimeAndSalesExtractionRequest works with ISINs but I am not sure why it doesn't work with US207932AB01. You need to contact the Refinitiv Tick History support team to verify what the problem is.
You can use the https://selectapi.datascope.refinitiv.com/RestApi/v1/Search/InstrumentSearch endpoint to search for the RICs of this ISIN.
{
"SearchRequest": {
"InstrumentTypeGroups": [
"CollatetizedMortgageObligations",
"Commodities",
"Equities",
"FuturesAndOptions",
"GovCorp",
"MortgageBackedSecurities",
"Money",
"Municipals",
"Funds"
],
"IdentifierType": "Isin",
"Identifier": "US207932AB01",
"PreferredIdentifierType": "Ric"
}
}The output is:
0
Answers
-
Thanks for reaching out to us.
I saw the same problem when using the TickHistoryTimeAndSalesExtractionRequest with this ISIN US207932AB01. The notes property shows the following information.
Instrument <ISN,US207932AB01> expanded to 0 RICS.\nInstrument <ISN,US207932AB01> expanded to 0 RICS.\n\nReport suppressed because there are no instruments
Please contact the Refinitiv Tick History support team directly via MyRefinitiv to verify what the problem is.
0 -
@Jirapongse Thanks for your reply, my understanding is that you can't request Time and Sales data by using an ISIN it must be a RIC. As we are unable to get the RIC from the Historical Request we can't then get the Time and Sales data.
0 -
Thank you, we have been looking at using the CMOABS Search which brings back the same results as the above instrument search. I have an open ticket with Refinitiv with, although they seem to think this is normal behavior which I disagree with.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 749 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
- 123 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛