Hi, on the DSS REST API, how do you search for indices from an Exchange (example: NAS) that belong t
Best Answer
-
Hello @austin.fan01 ,
My first and probably best suggestion will be to work with Refinitiv content experts to pinpoint the way to do this search via Datascope GUI. The approach that you come up with we will try to reproduce via DSS REST API.
Additionally, I would like to discuss a potential approach that I have researched:
The indices for NAS exchange can be identified, for example, via HistoricalCriteriaSearch
{{protocol}}{{host}}{{api}}Search/HistoricalCriteriaSearch
{
"Request": {
"RicPattern": null,
"BondTypeCodes": null,
"ContributorIds": null,
"CountryCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": ["43"],
"FutureMonthCodes": null,
"InstrumentTypeCodes": ["22","118"],
"OptionMonthCodes": null,
"OptionTypeCodes": null,
"CouponRate": null,
"StrikePrice": null,
"ExpiryDate": null,
"MaturityDate": null,
"Range": {
"Start": "2022-11-07T00:00:00.000Z",
"End": "2022-11-08T00:00:00.000Z"
}
}
}There is no provision to filter on request either on GICs or on TRBC codes.
If your indices are equity indices, you can also do:
{{protocol}}{{host}}{{api}}Search/EquitySearch
{
"SearchRequest": {
"AssetStatus": "Active",
"AssetCategoryCodes": ["EQI"],
"SubTypeCodes": null,
"CurrencyCodes": null,
"CompanyName": null,
"Description": null,
"DomicileCodes": null,
"ExchangeCodes": [ "NAS"],
"FairValueIndicator": null,
"FileCodes": null,
"GicsCodes": null,
"OrgId": null,
"Ticker": null,
"Identifier": null,
"IdentifierType": null,
"PreferredIdentifierType": null
}
}However, from my testing, GicsCodes filter will not be effective for indices- because for indices this content is not populated.
In step 2, Via TermsandConditionsRequest I request TRBC and GICS information on the indices RICs obtained from step 1:
{{protocol}}{{host}}{{api}}Extractions/ExtractWithNotes
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Currency Code","TRBC Business Sector Code","GICS Industry Code"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": ".BANKT", "IdentifierType": "Ric" },
{ "Identifier": ".NQPL60LMEURN", "IdentifierType": "Ric" },
{ "Identifier": ".NQASPA5010JPYN", "IdentifierType": "Ric" },
{ "Identifier": ".NQASPA5010LM", "IdentifierType": "Ric" }
]
}
}
}Resulting in:
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#DataScope.Select.Api.Extractions.ExtractionRequests.ExtractionResult",
"Contents": [
{
"IdentifierType": "Ric",
"Identifier": ".BANKT",
"RIC": ".BANKT",
"CUSIP": null,
"ISIN": null,
"SEDOL": null,
"Issuer OrgID": "70344",
"Currency Code": "USD",
"TRBC Business Sector Code": "5510",
"GICS Industry Code": null
},
{
"IdentifierType": "Ric",
"Identifier": ".NQPL60LMEURN",
"RIC": ".NQPL60LMEURN",
"CUSIP": null,
"ISIN": null,
"SEDOL": null,
"Issuer OrgID": "70344",
"Currency Code": "EUR",
"TRBC Business Sector Code": "5510",
"GICS Industry Code": null
},
{
"IdentifierType": "Ric",
"Identifier": ".NQASPA5010JPYN",
"RIC": ".NQASPA5010JPYN",
"CUSIP": null,
"ISIN": null,
"SEDOL": null,
"Issuer OrgID": "70344",
"Currency Code": "JPY",
"TRBC Business Sector Code": "5510",
"GICS Industry Code": null
},
{
"IdentifierType": "Ric",
"Identifier": ".NQASPA5010LM",
"RIC": ".NQASPA5010LM",
"CUSIP": null,
"ISIN": null,
"SEDOL": null,
"Issuer OrgID": "70344",
"Currency Code": "USD",
"TRBC Business Sector Code": "5510",
"GICS Industry Code": null
}
],I.e. TRBCs appear to be populated, while GICS are not.
Therefore, if one is able to come up with the list of required TRBCs, in step 3, one should be able to further filter the result from step 2, not request, but result, for example, keeping indices where TRBC = 5510
This approach may allow to arrive at the results you are looking for, but by working out the search via GUI and emulating it via API, you can potentially come up with a better solution. Once you have the GUI-driven approach- let us know, and we will try to help to migrate it to DSS REST API.
2
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 中文论坛