In DSS REST API, how can I specify the source for a CUSIP?

{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TimeSeriesExtractionRequest",
"ContentFieldNames": [
"File Code",
"RIC",
"Close Price",
"High Price",
"Low Price",
"Open Price",
"Bid Price",
"Ask Price",
"Universal Close Price"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "36729W509",
"IdentifierType": "Cusip"
}]
},
"Condition": {
"LastPriceOnly": false,
"StartDate": "2018-10-01T00:00:00.000Z",
"EndDate": "2018-10-18T00:00:00.000Z"
}
}
}
When my identifier in REST API/JSON is a cusip, how do I specify a source? My settings are set to default to EJV for hybrids, but there are times when I need to override that. For example, in the attached, I need to default this cusip to the .PK source. What do I need to add to my code to make this work?
Best Answer
-
You can filter on a source, using this syntax when defining the identifier:
{ "Identifier": "36729W509", "IdentifierType": "Cusip", "Source": "OTC" }
But note that the source must be an exchange code, not a RIC extension. For this particular Cusip I discovered the source is OTC, not PNK.
Does this help ?
0
Answers
-
Thanks very much, Christiaan. I've made this query public as well.
0 -
Thanks very much. So in this case, the API field name is "Source" - is there a full list of field names that I can reference for the future when building out these calls?
0 -
@Max.McDonough, you are welcome.
When you define an instrument identifiers list, there are no other fields (apart from the user defined ones, but they do not serve to select of filter things, they are only tags you can add in case you have your own internal references).
The API reference tree describes all API call fields, it is very useful. To discover what parameters can be used in API calls, I suggest you also look at this section of the Programming without SDK tutorial.
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 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
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛