Volatility Surfaces inputVolatilityType

Could someone please explain the difference between Implied and Quoted for inputVolatilityType on the surfaces API endpoint:
https://api.edp.thomsonreuters.com/data/quantitative-analytics-curves-and-surfaces/v1/surfaces
From API documentation page:
inputVolatilityTypeenumThe enumerate specifies the type of volatility used to build the surface.
- Quoted
- Implied
- Settle (deprecated)
From an older PDF (outdated)
inputVolatilityType Enumerate This enumerate specify if the generation of the volatility is done from the implied volatility calculated from the latest quote or from the settlement volatility from the previous close. The available values are: Implied, Settle.
Is it correct to assume that:
Implied - calculated from previous close (same as "Settle")
Quoted - calculated from latest quote (used to be "implied")?
Also, trying to relate these options to the Equity Volatility Surface Eikon app, are the Volatilty Type options there analagous to the API options?
Settlement IV (eikon) -> Implied (API)?
Mid IV (eikon) -> Quoted (API)?
Best Answer
-
Hello @paul.mcallister1
We are only able to answer technical API question on these forums. Here is an article on Instrument Pricing Analysis. If this information is not sufficient, I would recommend that you open a content support ticket at myRefinitiv.
0
Answers
-
Quoted - uses ready solution of analytics calculated IVs distributed directly to option FIDs, quicker and recommended if this solution is already exploited
Implied - calculated on the fly by our QPS, slower but may remove any model compatibility concerns raised by the above
0 -
The difference between “Quoted” and “Implied” is that “Implied” will compute implied volatilities on the fly, while “Quoted” will use volatility data that is already available as part of Refinitiv data.
What it means for our API users:- Surfaces with inputVolatilityType = “quoted” will be quicker to return results, and might be an interesting choice if they are already using Refinitiv volatilities.
- Surfaces with inputVolatilityType = “implied” can cover use cases where the volatility is not available or when an exchange only contributes a settlement price and not volatilities.
Both modes support Mid realtime calculations, settlement calculations and End of day close calculations.Currently the default is "implied" and this input is exploited in SURF app.
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
- 685 Datastream
- 1.4K DSS
- 615 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
- 252 ETA
- 556 WebSocket API
- 38 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
- 3 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.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛