HistoricalReferenceの欠損について

shiro.chiba
Newcomer
in TRTH
HistoricalReferenceレポートで、ESc1の満期日を取得しようとしています。
Expiration Dateは未設定であるため、Last Trading Dayを満期日として参照しようとしたのですが、
2021/3/19の満期日の情報が入っていません。
ESc1は3月、6月、9月、12月の第3金曜日が満期日であるため、上記の情報が欠損していると思うのですが、こちらはバグでしょうか?
また、過去データのみで発生しており、今後発生することはないでしょうか?
Tagged:
0
Best Answer
-
Thank you for reaching out to us.
Please try the "ETH Expiry Date" field.
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC",
"ETH Expiry Date"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "ESc1",
"IdentifierType": "Ric"
}
],
"ValidationOptions": {
"AllowHistoricalInstruments": true
},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "2021-05-01",
"QueryEndDate": "2023-10-31"
}
}
}The output is:
...
{
"IdentifierType": "Ric",
"Identifier": "ESc1",
"RIC": "ESc1",
"ETH Expiry Date": "2023-03-17"
},
{
"IdentifierType": "Ric",
"Identifier": "ESc1",
"RIC": "ESc1",
"ETH Expiry Date": "2023-06-16"
},
{
"IdentifierType": "Ric",
"Identifier": "ESc1",
"RIC": "ESc1",
"ETH Expiry Date": "2023-06-16"
},
{
"IdentifierType": "Ric",
"Identifier": "ESc1",
"RIC": "ESc1",
"ETH Expiry Date": "2023-09-15"
},
{
"IdentifierType": "Ric",
"Identifier": "ESc1",
"RIC": "ESc1",
"ETH Expiry Date": "2023-09-15"
},
{
"IdentifierType": "Ric",
"Identifier": "ESc1",
"RIC": "ESc1",
"ETH Expiry Date": "2023-12-15"
},0
Answers
-
@Jirapongse ご回答ありがとうございます。
上記のリクエストを行うと、400エラーが発生しました。
'{"error":{"message":"Validation Error:\\r\\n\\r\\nInvalid content FieldName \\"ETH Expiry Date\\"V}'
pythonでリクエストを行ったのですが、Bodyは以下の内容になります。
url = 'https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotes';
headers =
'Prefer': 'respond-async
'Content-Type': 'application/json
'Authorization': f'Token {token
}
data = {
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC",
"ETH Expiry Date"
],
"IdentifierList":
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers":[
{
"Identifier": "ESc1",
"IdentifierType": "Ric"
}
],
"ValidationOptions": {"AllowHistoricalInstruments": True},
"UseUserPreferencesForValidationOptions": False
},
"Condition":
"ReportDateRangeType": "Range",
"QueryStartDate": {start_date},
"QueryEndDate": {end_date}
}
}
response = requests.post(url, data=json.dumps(data), headers=headers)何か間違ってますでしょうか?
0 -
The request message is not a valid JSON.
The code should look like this:
import requests
import json
url = "https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotes"
payload = json.dumps({
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC",
"ETH Expiry Date"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "ESc1",
"IdentifierType": "Ric"
}
],
"ValidationOptions": {
"AllowHistoricalInstruments": True
},
"UseUserPreferencesForValidationOptions": False
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "2020-01-01",
"QueryEndDate": "2023-01-01"
}
}
})
headers = {
'Prefer': 'respond-async',
'Content-Type': 'application/json',
'Authorization': 'Token <token>'
}
response = requests.request("POST", url, headers=headers, data=payload)
print(response.text)0 -
0
-
@shiro.chiba
This is strange. This field may be an internal field.
Please contact the Refinitiv Tick History support team directly via MyRefinitiv to verify this field or get another field that can provide the same data.
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 中文论坛