Given Ric code of put option can we identify its call options Ric code and vise versa.
Answers
-
Hi @jay416505,
I'm not sure if I understand the question correctly. Do you mean you want to get RIC name have the same strike price, expiration date, etc, but opposite options?
Generally, there is RIC rule to construct Options RIC. You may use the rules to reconstruct RIC.
Anyway, for REST API, you may use the following instructions for FuturesAndOptionsSearchRequest to get information and use the information to search of opposite Call/Put.
1. Get attributes of a given RIC (i.e. SPXCC202001750.U)
Request:
{
"SearchRequest": {
"FileCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": null,
"StrikePrice": null,
"ExpirationDate": null,
"IdentifierType": "Ric",
"Identifier": "SPXCC202001750.U",
"PreferredIdentifierType": "Ric",
"UnderlyingRic": null,
"AssetStatus": "Active",
"PutCall": null
}
}Response:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.FuturesAndOptionsSearchResult)",
"value": [
{
"Identifier": "SPXCC202001750.U",
"IdentifierType": "Ric",
"Source": "OPQ",
"Key": "VjF8MHgwMDEwMGIwMDFkYWQwOGI4fDB4MDAxMDBiMDAxZGFiODMzNHxPUFF8RFZRVXxERVJWfE9QVHxEfHxTUFhDQzIwMjAwMTc1MC5VfDcxNTQ",
"Description": "SPXC Mar0 17.5 C",
"InstrumentType": "DerivativeQuote",
"Status": "Valid",
"ExchangeCode": "OPQ",
"CurrencyCode": "USD",
"FuturesAndOptionsType": "Options",
"PutCallCode": "Call",
"ExpirationDate": "2020-03-20T00:00:00.000Z",
"StrikePrice": 17.5,
"AssetStatus": "Active"
}
]
}2. Use the returned information such as ExpirationDate and StrikePrice, but use opposite PutCall for the search.
Request:
{
"SearchRequest": {
"FileCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": null,
"StrikePrice": {
"@odata.type": "#ThomsonReuters.Dss.Api.Search.NumericValueComparison",
"Value": 17.5
},
"ExpirationDate": {
"@odata.type": "#ThomsonReuters.Dss.Api.Search.DateValueComparison",
"Value": "2020-03-20T00:00:00.000Z"
},
"IdentifierType": "Ric",
"Identifier": "SPX*",
"PreferredIdentifierType": "Ric",
"UnderlyingRic": null,
"AssetStatus": "Active",
"PutCall": "Put"
}
}Response:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.FuturesAndOptionsSearchResult)",
"value": [
{
"Identifier": "SPXCO202001750.U",
"IdentifierType": "Ric",
"Source": "OPQ",
"Key": "VjF8MHgwMDEwMGIwMDFkYWQxMWUwfDB4MDAxMDBiMDAxZGFiOTgyYXxPUFF8RFZRVXxERVJWfE9QVHxEfHxTUFhDTzIwMjAwMTc1MC5VfDcxNTQ",
"Description": "SPXC Mar0 17.5 P",
"InstrumentType": "DerivativeQuote",
"Status": "Valid",
"ExchangeCode": "OPQ",
"CurrencyCode": "USD",
"FuturesAndOptionsType": "Options",
"PutCallCode": "Put",
"ExpirationDate": "2020-03-20T00:00:00.000Z",
"StrikePrice": 17.5,
"AssetStatus": "Active"
}
]
}0 -
This is not what I expect
e.g 1
Input ric - SPXo202031450.U
output Ric -
e.g 2
Input ric - SPXc202031450.U
output Ric -
SPXo202031450.U
0 -
Hi @jay416505,
I would like to better understand the requirement. Could you elaborate and provide the sample of expected result?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 704 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.3K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 568 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
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 871 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛