Retrieving RIC Contract Year and Month
Hello,
I was wondering if there are "ContentFieldNames" for contract year and month? Using [second last, last] characters in the RIC for [month, year] is sometimes unreliable for me, since I have instruments that expire in 10+ years (e.g. NGZ34 for natural gas December 2034). I would prefer not to implement my own parsing logic if not necessary.
Using "Expiration Date" isn't plausible either. For example, CLZ2 (light crude December 2022) expires 2022-11-21.
Sample Query:
{"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC", "RIC Root", "Underlying RIC", "Security Description", "Periodicity",
"First Trading Date", "First Notice Day", "Last Trading Day", "Expiration Date"],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "0#CL:",
"IdentifierType": "ChainRIC"
}
]
}
}
}
Thanks!
Best Answer
-
Hello @jacktan ,
Considering the difference in the results that you observe, and there are a couple of possible explanations to the different result with the exact same request, that I can think of:
1. Permissions could be different. You could run the same request via DSS GUI and to see if you are able to obtain the complete result. I suggest to open a support ticket with DSS support via Refinitiv Helpdesk Online -> Product -> DSS to verify that your user ID is permissioned to retrieve this field for this chain.
2. Are you testing the request with a naked request via Postman or via custom code? If from custom code, after you are confirmed to be permissioned for the field, I would test with Postman "naked" request to avoid any potential code discrepancy causing the lack of the result. Please refer to Postman tutorial REST API Tutorial 7: On Demand T&C extraction and starter Postman request collection can be downloaded from DSS REST Downloads to enable a quick test.
Let us know how this works on your side and if we could be of more help?
0
Answers
-
Hello @jacktan ,
Try with:
{"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC", "RIC Root", "Underlying RIC", "Security Description", "Periodicity",
"First Trading Date", "First Notice Day", "Last Trading Day", "Expiration Date","Contract Month and Year"],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "0#CL:",
"IdentifierType": "ChainRIC"
}
]
}
}
}Results should look like:
...
{
"IdentifierType": "ChainRIC",
"Identifier": "0#CL:",
"RIC": "CLZ2",
"RIC Root": "CL",
"Underlying RIC": null,
"Security Description": "LIGHT CRUDE DEC2",
"Periodicity": "M",
"First Trading Date": "2013-11-20",
"First Notice Day": "2022-11-23",
"Last Trading Day": "2022-11-21",
"Expiration Date": "2022-11-21",
"Contract Month and Year": "DEC2022"
},
...Is this what you are looking for?
0 -
I tried adding "Contract Month and Year" like you suggested, but it only returned "None".
Please see image below.
My request to "/Extractions/ExtractWithNotes":
{"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC", "Contract Month and Year", "Security Description",
"First Trading Date", "First Notice Day", "Last Trading Day", "Expiration Date"],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "0#CL:",
"IdentifierType": "ChainRIC"
}
]
}
}
}Thanks!
0 -
After raising a ticket with a product specialist, this was the final verdict:
'Contract Month and Year' field is not supported for Tick History users. As an alternative you may use the Expiry date field in 'Historical Reference' and 'Elektron Time Series' report templates.
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
- 280 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
- 721 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 中文论坛