How to perform on-demand Terms and Conditions extract using IdentifierType.Ticker
Is it possible to use IdentifierType.Ticker when performing an on-demand extraction? I'm using the following code:
var ExtractionsContext = new ExtractionsContext(new Uri("https://hosted.datascopeapi.reuters.com/RestApi/v1/"), "<your user id>", "<your password>");
//Create new report template with conditions
var extractionRequest = new TermsAndConditionsExtractionRequest {
IdentifierList = InstrumentIdentifierList.Create(
new[] { new InstrumentIdentifier { Identifier = "MSFT", IdentifierType = IdentifierType.Ticker } }, null, false),
ContentFieldNames = new[]
{
"Ticker",
"Asset Type Description",
"Security Description",
"Issue Date",
"RIC",
"Asset Status Description",
"Asset SubType Description",
"Currency Code Description",},
};
//Extract - NOTE: If the extraction request takes more than 30 seconds the async mechansim will be used. See Key Mechanisms
var extractionResult = ExtractionsContext.ExtractWithNotes(extractionRequest);
var extractedRows = extractionResult.Contents;
//Output
if (!extractedRows.Any())
Debug.WriteLine("No rows returned");
else {
foreach (var row in extractedRows)
Debug.WriteLine(
row.Identifier + " (" + row.IdentifierType + ") " +
String.Join(", ", row.DynamicProperties.Select(dp => dp.Key + "=" + dp.Value)));
}
//Output Notes
Debug.WriteLine("NOTES:");
foreach (var note in extractionResult.Notes)
Debug.WriteLine(note);
The results come back with the following message: MSFT (Ticker)
NOTES:
All identifiers were invalid. No extraction performed.
Is it not possible? If not, any alternate approach would be most welcome.
Best Answer
-
I have used Search/InstrumentSearch with Postman and it works fine with Ticker.
{
"SearchRequest": {
"InstrumentTypeGroups": [
"CollatetizedMortgageObligations",
"Commodities",
"Equities",
"FuturesAndOptions",
"GovCorp",
"MortgageBackedSecurities",
"Money",
"Municipals",
"Funds"
],
"IdentifierType": "Ticker",
"Identifier": "MSFT",
"PreferredIdentifierType": "Ric"
}
}The response is:
{
"Identifier": "MSFT.MW",
"IdentifierType": "Ric",
"Source": "GSM",
"Key": "VjF8MHgwMDAzZGQwMDEzNWZiNzI1fDB4MDAwM2RjMDAzNDdiYjgyOHxHU018RVFRVXxFUVRZfE9EU0h8RXx8TVNGVC5NV3wxMTcw",
"Description": "MICROSOFT ORD",
"InstrumentType": "EquityQuote",
"Status": "Valid"
},
{
"Identifier": "MSFT.OQ",
"IdentifierType": "Ric",
"Source": "NSM",
"Key": "VjF8MHgwMDAzZGQwMDEzNWZiNzI1fDB4MDAwM2RjMDAzOGRlMmIxMnxOU018RVFRVXxFUVRZfE9EU0h8RXx8TVNGVC5PUXwxMzAz",
"Description": "MICROSOFT ORD",
"InstrumentType": "EquityQuote",
"Status": "Valid"
},
...Please share your code for search.
0
Answers
-
I got the same result as yours. It returned "Not found".
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionRow)",
"value": [
{
"IdentifierType": "Ticker",
"Identifier": "MSFT",
"Error": "Not found"
}
]
}Please directly contact DSS support team via Contact Us to verify the problem.
You may use search to find RICs for MSFT and then use those RICs with TermsAndConditionsExtractionRequest.
0 -
Thanks for your reply @jiraponse.phuriphanvchai. With large dynamic lists of securities it would be great to avoid search. I understand tickers are used differently based on exchange and asset type. It would be great to extract based on a combination of exchange, type and ticker. I'll reach out to support.
0 -
I tried search and no luck. "The identifier Type TICKER is not supported..."
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
- 715 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 中文论坛