API Code to Filter data using Exchange Code
Hello,
My client is using TRTH REST API, with the below code he is trying to extract Historical Reference Data using SEDOL, he would like to further filter his result to only to a specific exchange.
Could you please help me with the filtering option.
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC", "Asset Category", "Primary Trading RIC", "CUSIP", "SEDOL", "ISIN", "Issuer OrgID", "Exchange Code", "Currency Code", "Change Date"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "6456403", "IdentifierType": "Sedol" }
],
"ValidationOptions": {"AllowHistoricalInstruments": true},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "1996-01-01",
"QueryEndDate": "2018-12-31"
}
}
}
Thanks,
Praveen Rangaiah
Best Answer
-
The historical reference API call does not allow filtering by exchange.
Potential solutions
- Programmatically filter the results, to keep only those where the Exchange Code field has the desired value. This is straightforward and fairly easy.
- Depending on the use case, maybe your customer could use a T&C (Terms and Conditions) request, which allows filtering on an exchange by using the Source field for the identifier:
{ "Identifier": "6456403", "IdentifierType": "Sedol", "Source": "TYO" }
Warning: there are several caveats to the T&C approach:
- A T&C request only delivers the current mapping for the primary RIC, whereas the Historical Reference call delivers historical mappings.
- For a T&C request field Change Date does not exist, but there is a Last Change Date field. All the other fields of your request are available.
0
Answers
-
@Christiaan Meihsl Thanks a lot for the API code.
So, this code works only for T&C template and not for Historical Reference. Is there no option for client to filter using Exchange code for Historical Reference template.
0 -
Praveen.Rangaiah, as stated, the historical reference API call does not allow filtering by exchange. If you want to use that call then you will have to programmatically filter the results (which is fairly easy).
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 中文论坛