Is there any way to resolve the RIC code based on RIC root for futures via API?

Hi , It seems that to pull the prices via API for any future we have to setup RIC Code per Maturity level and request. Is it possible to somehow just filter with RIC roots and get all futures RIC code resolve automatically? Let's say for NGMM RIC root can we receive the prices for all Futures without setting up individual RIC code per maturity level e.g.
NGMMc2
NGMMc3
---- so on.
Best Answer
-
Thanks for reaching out to us.
You can try the /Search/FuturesAndOptionsSearch endpoint. The request message looks like this:
{
"SearchRequest": {
"FileCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": null,
"StrikePrice": null,
"ExpirationDate": null,
"IdentifierType": "RICRoot",
"Identifier": "NGMM",
"PreferredIdentifierType": "Ric",
"AssetStatus": "Active"
}
}You can specify the odata.maxpagesize in the Prefer HTTP header to 500 to get all results without paging.
The output looks like this:
For more information regarding the parameters of the /Search/FuturesAndOptionsSearch endpoint, please refer to the REST API Reference Tree.
I hope this will help.
0
Answers
-
@Jirapongse Thank you for prompt reply. I tried and it's working at my end. I have one more question. Can we also get the RIC code only subscribed or pay by my client? For e.g. same NGMM RIC root , my client wants only prices for few maturity months until 2024 Dec. How can we avoid request for RIC code where my client doesn't want price for ?
0 -
You can set the expiration date.
{
"SearchRequest": {
"FileCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": null,
"StrikePrice": null,
"ExpirationDate": {
"@odata.type": "#DataScope.Select.Api.Search.DateRangeComparison",
"From": "2023-01-10T00:00:00.000Z",
"To": "2024-01-31T00:00:00.000Z"
},
"IdentifierType": "RICRoot",
"Identifier": "NGMM",
"PreferredIdentifierType": "Ric",
"AssetStatus": "Active"
}
}Please refer to the REST API Reference Tree for other parameters and usages.
0 -
Hi, Thanks for the help again. I tried to search 5-6 RIC code based on the root available. However for Ric Root = PROCNWEM , The response give {} could you please help me why I am not getting Ric Code for this root?
"IdentifierType": "RICRoot",
"Identifier": "PROCNWEM",
"PreferredIdentifierType": "Ric",
"AssetStatus": "Active"
0 -
You can try the Search/CommoditySearch endpoint.
The request looks like this:
{
"SearchRequest": {
"KeywordQuery": "PROCNWEM",
"AssetStatus": "Active",
"PreferredIdentifierType": "Ric"
}
}The output is:
0 -
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 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
- 2 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.8K Refinitiv Data Platform
- 622 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
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛