FX volatility smile

Hi,
I have a doubt regarding the volatility smile that can be retrieved through the quantitative-analytics-curves-and-surfaces/v1/surfaces endpoint. I am making the http request with this body:
{
"universe": [
{
"underlyingType": "Fx",
"surfaceTag": "FxVol-GBPEUR",
"underlyingDefinition": {
"fxCrossCode": "GBPEUR"
},
"surfaceLayout": {
"format": "Matrix"
},
"surfaceParameters": {
"xAxis": "Date",
"yAxis": "Strike",
"calculationDate": "2018-08-20T00:00:00Z",
"returnAtm": true
}
}
]
}
When I change the fxCrossCode to EURGBP, since the strikes of the response are very similar, I expected to get the same volatility data, but it didn't happen. I realized that the strikes are not exactly the same when fxCrossCode is changed, so I plotted the smile for the 02/08/2018 expiry, and this is the result.
I would like to understand why these smiles are different. Thanks in advance.
Best Answer
-
I have raised a case with Refinitiv Helpdesk on your behalf for this issue. For your reference the case number is 10125413.
The root cause of the problem will need to be confirmed by the support team. But as I see it, the service appears to return incorrect values for the strikes when inverse currency pair is used in the request. For GBPEUR currency pair the values of the strikes should be greater than 1. It seems that the service instead returns the strikes for regular EURGBP pair, which are less than 1. The shape of the smile returned for GBPEUR looks correct to me. It should be a mirror image of the smile for EURGBP. But it should be plotted against the strikes for GBPEUR, not against the strikes for EURGBP. And if one were to inverse the strikes for GBPEUR and plot the corresponding volatilities against inverted strikes, then the resulting curve should match the curve returned for EURGBP.
Refinitiv Support team will investigate the issue. They will reach out to you, should they have any questions, and to keep you informed of their progress.0
Answers
-
0
-
Hello @YERAY SOSA ALONSO
I checked case 10125413, the issue with /data/quantitative-analytics-curves-and-surfaces/v1/surfaces endpoint was fixed. Could you please confirm?
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
- 684 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
- 249 ETA
- 554 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
- 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
- 643 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛