How to get "Option Watch Implied vols" in python api?
I noticed that in Eikon DIB, the fields "TR.OPWBidImpliedVolatility", "TR.OPWAskImpliedVolatility" reflect different implied vols compared to 'TR.IMPLIEDVOLATILITYOFBIDPRICE','TR.IMPLIEDVOLATILITYOFASKPRICE' (e.g. check EMBA172011400.U). On the one hand, I'm not sure what's the difference between those two sets of the fields. On the other hand, would like to ask what is the right way to access the"OPW" implied vols in python api, given an option chain ticker (something like '0#EMB*.U')?
Best Answer
-
Hi @xiang.zhang,
When asking questions related to data, the best resource is to use the Refinitiv HelpDesk which you can reach by either using Contact Us capability in your Eikon application or by calling the Helpdesk number in your country. The moderators on this forum do not have deep expertise in every type of content available through Eikon. The Helpdesk will research your question and will get back to you.
As for your question, I believe the implied volatility values can be found in the BID and ASK fields. Please see this thread for more details. You can request for the option chain ticker as:
I would further verify with the Help Desk.
0
Answers
-
Hi Nick, sorry but I believe the 'Bid' and 'Ask' in the screenshot are prices (implied vol of those options cannot be 0).
Understood I should direct questions about diff of field to Helpdesk, and I have done that and understand now that one is implied vol computed from last price, the other is from mid price.
But the second part of the question is still not clear (how to access those fields in python api). In past experience, regarding python api questions, I have always been directed to this forum by helpdesk.
0 -
Hi @xiang.zhang,
If you construct your questions in such a way that simply asks which fields will contain the values that you want, the helpdesk should not be directing you to this forum. If you frame the question in such a way where you ask which API do I need to use..., then they will instruct you to come here. Try to keep your data questions specific to fields, not API related.
As for the second part, the above formula I provided is how you get fields using the Python API. You just need to supply valid fields that provide you with the data values of interest or allow you to compute the values of interest.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛