Settings source/exchange/composite python

Hi all,
I am trying to get intraday data via TRTH for a number of instruments (GILTs). I am only interested in composite data, not single sources. I am using ISINs as my IdentifierType.
Thus, first, I would like to know which source code is the right one for refinitiv composite data.
Secondly, it seems that even when I set a source in:
self.instrumentsid = [{"Identifier": i, "IdentifierType": self.identifier_type, "Source": self.source} for i in self.instruments]
with
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": self.instrumentsid,
"UseUserPreferencesForValidationOptions":"false"
}
The request is nonetheless expanding anyway, which is really concerning tbh.
Instrument <ISN,GB00BDRHNP05> expanded to 29 RIC instances: CH35928402=S to GBTSY28=SMKR. Instrument <ISN,GB00BZB26Y51> expanded to 34 RIC instances: CH34468946=S to GBTSY31=SMKR.
So how to avoid expanding RIC instances? Is an ISIN, an IdentifierType and a source not enough to get only one RIC?
Many thx
Best Answer
-
Hello @kevin.ferret,
REST API Reference Tree is the complete reference of available Datascope requests, login with your RTH user id and password,
You can look up the spec of on-demand request by selecting
Extractions -> On Demand Extraction -> ExtractRaw
And select the request to look up from the drop-down list of available requests on the right. This should show request spec, result spec and specific examples.
Datascope backend is shared by the two products, Refinitiv Tick History ( RTH) and Datascope Select (DSS). As your user is permissioned for RTH, and not DSS, RTH requests will be available to you. Both Intraday and EOD requests are part of RTH.
---
I would like to clarify that RICs are not expanded. Chain RICs and ISINs are expanded. If you would like the identifier to be requested as is, you would supply RICs directly, for example:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryIntradaySummariesExtractionRequest",
"ContentFieldNames": [
"Close Ask",
"Close Bid",
"High",
"High Ask",
"High Bid",
"Last",
"Low",
"Low Ask",
"Low Bid",
"No. Asks",
"No. Bids",
"No. Trades",
"Open",
"Open Ask",
"Open Bid",
"Volume"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "CARR.PA",
"IdentifierType": "Ric"
}],
"ValidationOptions": null,
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"MessageTimeStampIn": "GmtUtc",
"ReportDateRangeType": "Range",
"QueryStartDate": "2016-09-29T00:00:00.000Z",
"QueryEndDate": "2016-09-30T00:00:00.000Z",
"SummaryInterval": "OneHour",
"TimebarPersistence": true,
"DisplaySourceRIC": true
}
}
}0
Answers
-
Hi thx for replying.
below the body:
@{'ExtractionRequest': {'@odata.type': '#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryIntradaySummariesExtractionRequest',
'ContentFieldNames': ['Close Ask', 'Close Bid', 'High', 'High Ask', 'High Bid', 'Last', 'Low', 'Low Ask', 'Low Bid', 'No. Asks', 'No. Bids', 'No. Trades', 'Open', 'Open Ask', 'Open Bid', 'Volume'],
'IdentifierList': {'@odata.type': '#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList',
'InstrumentIdentifiers': [{'Identifier': 'GB00BDRHNP05', 'IdentifierType': 'Isin', 'Source': 'L'}],
'UseUserPreferencesForValidationOptions': 'false'},
'Condition': {'MessageTimeStampIn': 'GmtUtc', 'ReportDateRangeType': 'Range', 'QueryStartDate': '2018-01-08T00:00:00Z', 'QueryEndDate': '2018-01-10T00:00:00Z', 'SummaryInterval': 'OneMinute', 'TimebarPersistence': 'true', 'DisplaySourceRIC': 'true'}}}Many thx
0 -
Hi thx for replying. See below. Many thx
0 -
Hi @kevin.ferret,
By submitting TickHistoryIntradaySummariesExtraction requests, if your Identifier type is either ISIN on ChainRIC, it will get expanded into multiple RICs.
- To avoid the expansion, you may wish to submit one or more specific RICs as identifier to TickHistoryIntradaySummariesExtraction.
- There may be a request that is more suitable to your requirements (I am a developer, so may be lacking some nuances in content understanding) - I would try EOD:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest",
"ContentFieldNames": [
"Instrument ID",
"Open",
"High",
"Low",
"Last",
"Volume",
"VWAP",
"Number of Price Moves",
"Trade Date"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{"Identifier": "GB00BDRHNP05", "IdentifierType": "Isin"}
]
},
"Condition": {
"StartDate": "2018-01-08T00:00:00Z", "EndDate": "2018-01-10T00:00:00Z"
}
}
}That does not expand, results in:
Instrument ID,Open,High,Low,Last,Volume,VWAP,Number of Price Moves,Trade Date
GB00BDRHNP05,99.72,99.97,99.6,,,,,2018/01/08
GB00BDRHNP05,99.91,99.91,99.34,,,,,2018/01/09
GB00BDRHNP05,99.53,99.53,99.17,,,,,2018/01/10- Also, to obtain a definitive answer on the correct content request, per your requirements, from one of Refinitiv content experts, as a customer, you can contact Refinitiv Helpdesk Online -> Content -> RTH directly.
0 -
Thx,
In your code I see that even if you use {"Identifier": "GB00BDRHNP05", "IdentifierType": "Isin"} it is not expanding right? So what else did you change compared to my previous message (body) to have this result?
Many thx
0 -
Hi @kevin.ferret,
This is a different request type, ElektronTimeseriesExtractionRequest, with the different interface spec, please see the above request.
BTW, in the question you said you were requesting composite, so I have tested CompositeExtractionRequest, and did not see what you were seeing. It was because you were running TickHistoryIntradaySummariesExtractionRequest request.
0 -
Thx for that. So where are the list of endpoints? I just tried CompositeExtractionRequest and got an error (I am probably making a mistake somewhere). So to be sure, you were able to request intraday market data for the ISIN above using the composite request?
Many thx
0 -
ElektronTimeseriesExtractionRequest seems to be for EOD. What about Intraday? Could you pleae provide me an example for an intraday request without RICs expansion? Many thx
0 -
Hi @Kevin.ferret,
We have GovCorp Search helps to arrive at CPL source specific RIC from ISIN. Below is the example:
End Point:
<https://hosted.datascopeapi.reuters.com/RestApi/v1/Search/GovCorpSearch >Body:
{
"SearchRequest": {
"AssetStatuses": [
"TEN",
"RES",
"REP",
"FDD",
"RBM",
"RMK",
"RPN",
"PUT",
"PRE",
"NAC",
"LIQ",
"ISS",
"DEF",
"FNG",
"MAT",
"EXC",
"RDM",
"DFS",
"CAN",
"CLD"
],
"Coupon": null,
"CurrencyCodes": null,
"GovCorpContributorCode" : "CPL",
"Group": {
"Agency": true,
"Government": true,
"Corporate": true,
"Supra": true},
"MoodyRatingsCodes": null,
"StandardPoorsRatingsCodes": null,
"Callable": false,
"Convertable": false,
"Extendable": false,
"Putable": false,
"Sinkable": false,
"IssueDate": null,
"MaturityDate": null,
"NextPayDate": null,
"Ticker": null,
"IdentifierType": "Isin",
"Identifier": "GB00BDRHNP05",
"PreferredIdentifierType": "Ric"
}
}
Response:{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Content.ValidatedInstrument)",
"value": [
{
"Identifier": "GBT1Q27=",
"IdentifierType": "Ric",
"Source": "CPL",
"Key": "VjF8MHgwMDEwMmM4YmU1OGEwY2Q0fDB4MDAxMDJjODk2OGE4MGM3OXxDUEx8R0NCRHx8fEd8RXxHQlQxUTI3PXw",
"Description": "GBGV 1.250 07/22/27",
"InstrumentType": "GovCorpBond",
"Status": "Valid"
}
]
}
Once you have this composite RIC in your results, you may do a API call to get Tick Data{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryIntradaySummariesExtractionRequest",
"ContentFieldNames": ["Close Ask", "Close Bid", "High", "High Ask", "High Bid", "Last", "Low", "Low Ask", "Low Bid", "No. Asks", "No. Bids", "No. Trades", "Open", "Open Ask", "Open Bid", "Volume"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "GBT1Q27=", "IdentifierType": "Ric" }
],
"ValidationOptions": null,
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"MessageTimeStampIn": "GmtUtc",
"ReportDateRangeType": "Range",
"QueryStartDate": "2021-02-22T00:00:00.000",
"QueryEndDate": "2021-02-23T00:00:00.000",
"SummaryInterval": "OneMinute",
"TimebarPersistence": true,
"DisplaySourceRIC": true
}
}
}
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 698 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 257 ETA
- 565 WebSocket API
- 40 FX Venues
- 16 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
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.1K Refinitiv Data Platform
- 800 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 232 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 101 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛