How to append historical instruments to an instrument list through the REST API?

From the Tick History User Guide, to add an Instrument to a list we provide this body:
{
"Identifiers": [
{
"@odata.type": "#ThomsonReuters.Dss.Api.Search.HistoricalSearchResult",
"Identifier": "IBM.N",
"IdentifierType": "Ric"
}
],
"KeepDuplicates": true
}
Is there any body key value for allowing historical instruments? (Like we have on OnDemmand requests: "ValidationOptions": {
"AllowHistoricalInstruments": true
}) Where can I find all key values for this add instrument request body?
Best Answer
-
To be able to append a historical instrument, you need to change the user preferences, to enable "Allow Import of Historical Instruments". This can be done in the user preferences GUI:
Once that is done your append command via the API will work fine.
0
Answers
-
Hello @rodrigogaf,
Depending on what request you are looking to use.
Are you looking to run HistoricalSearch request
{{protocol}}{{host}}{{api}}Search/HistoricalSearch
?
Then there can only be one instrument passed, but the result will return the found instruments within date range in history, without specifying additional validation options such as AllowHistoricalInstruments = true
{
"Request": {
"Identifier": "US4592001014",
"IdentifierType": "Isin",
"Range": {
"Start": "2008-01-01T00:00:00.000Z",
"End": "2008-01-01T00:00:00.000Z"
}
}
}Are you looking to run Historical Reference Extraction
{{protocol}}{{host}}{{api}}Extractions/Extract
?
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Exchange Code", "Currency Code", "Change Date"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "00209tab1",
"IdentifierType": "Cusip"
},
{
"Identifier": "IBM.N",
"IdentifierType": "Ric"
},
{
"Identifier": "US4592001014",
"IdentifierType": "Isin"
},
{
"Identifier": "B1YW440",
"IdentifierType": "Sedol"
}
],
"ValidationOptions": {"AllowHistoricalInstruments": true},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"StartDate": "2017-05-01T00:00:00.000Z",
"EndDate": "2017-05-31T23:59:59.000Z"
}
}
}Then you will pass the ValidationOptions like above.
I hope this helps, otherwise, please indicate what request you are asking about.
0 -
Not solved yet. This is my request:
POST https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/InstrumentLists('MY_INSTRUMENT_LIST_ID')/ThomsonReuters.Dss.Api.Extractions.InstrumentListAppendIdentifiers
Authorization: Token
Content-Type: application/json
Accept-Charset: UTF-8
Prefer: respond-async
{
"Identifiers": [
{
"@odata.type": "#ThomsonReuters.Dss.Api.Search.HistoricalSearchResult",
"Identifier": "DOLF18",
"IdentifierType": "Ric"
}
],
"KeepDuplicates": true
}As I see, with this request I want the expired future contract with Ric 'DOLF18' in the instrument list associated with the ID: 'MY_INSTRUMENT_LIST_ID'. When I run this request I get 'Ric not found'.
However, the Ric exists and can be found with a Historical Search in DataScope where I can add it manually to my instrument list, but I want to add through the REST API.
So, my question is: How can I and add historical instruments to my instruments list trough the REST API using the end point bellow?
https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/InstrumentLists('MY_INSTRUMENT_LIST_ID')/ThomsonReuters.Dss.Api.Extractions.InstrumentListAppendIdentifiers
Is there any parameters that I should add in my request body?
Thank you!0 -
Thank you @Christiaan Meihsl! It works now.
0 -
Great, glad to hear that :-)
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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛