passing market segment code and country exchange code via the instrumentidentifier object
Hi,
im trying to get similar data using the rest api comparing to the sftp file submit.
one of the values we are sending via the dss sftp is the market segment code or the country exchange code that are basically changing the market stock exchange.
what is the way to send these parameters via the instrumentidentifiers, I managed to pass user identifier, identifiertype, and the identifier but didn't find when to post these market segment code and the country exchange code via these object related to the reporttemplatetype composite.
for example in the sftp I will get the ric US.0001 while in the rest api I will get HK.0001 for the same identifier
thank you for any assistance
Y.D
Best Answer
-
InstrumentIdentifiers type doesn't have the market segment code and country exchange code properties. It provides the Source property. Please refer to this thread regarding how to use this property.
You can use search in the REST API to search for instruments. For example, you can specify the DomicileCodes and ExchangeCodes in the /Search/EquitySearch.
You also specify the InstrumentTypeGroups in the /Search/InstrumentSearch.
For more information about Search, please refer to the REST API Reference Tree.
After getting results from the Search API, you can use the returned instruments with the On-Demand extraction.
0
Answers
-
Hi Zoya,
thank you for the respond,
we are using both the composite world.
in the ftp method we are sending 3 files -
1.xml including struct of the fields we request
2.xml including scheduling on when we would like to extract the report
3.csv including 4 fields - user id, instrument id, instrument type id, optional field including country exchange code or market segment code.
for now lets igore the scheduling xml
via the rest api the implementation is as follow -
var availableFields = ExtractionsContext.GetValidContentFieldTypes(ReportTemplateTypes.Composite);
var extractionRequest = new CompositeExtractionRequest
{
IdentifierList = InstrumentIdentifierList.Create(
new[]
{
new InstrumentIdentifier {
Identifier = "191216100",
IdentifierType = IdentifierType.Cusip,
UserDefinedIdentifier = "AA" }
}, null, false),
new[]
{
//same fields requested in the ftp
}
var extractionResult = ExtractionsContext.ExtractWithNotes(extractionRequest);
var extractedRows = extractionResult.Contents;
Yaniv
0 -
Hi,
how to implement instrument validity,
I understood that the fields i want to use as a coditions are part of GUI configuratiob but I would like to implement them via the sdk,
thanks
0 -
Hi jirapongse,
thank you for the answer, just to clear it, it means I can use the source property for pricing source/exchange country code and segment code?
0 -
You can not use the source/exchange country code and segment code in the On-Demand request extraction.
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
- 24 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
- 713 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 中文论坛