Apparent inconsistency in GPB Libor 6M ZC curve

Good Morning,
I am using RDP to retrieve GBP Libor 6M curve, and I have noticed that there is a difference with the data that I get from the Eikon Desktop Application using the RIC for Zero Coupon Curves 0#GBPSBSLZ=R. I would appreciate if you could explain me the reasons for the difference that I am going to show now.
In RDP, I am using the endpoint: https://api.refinitiv.com/data/quantitative-analytics-curves-and-surfaces/v1/curves/zc-curves, with the following body:
{ "universe": [ { "curveParameters": { "valuationDate": "2021-12-31", "priceSide": "Mid", "interpolationMode": "CubicDiscount" }, "curveDefinition": { "currency": "GBP", "indexName": "LIBOR", "name": "GBP LIBOR Swap ZC Curve", "source": "Refinitiv", "discountingTenor": "OIS" } } ], "outputs": [ "Constituents", "DetailedCurvePoint", "UnderlyingCurves" ]}
I am going to focus in the differences for the 20Y point. The 20Y point obtained from the API is:
{ "endDate": "2041-12-31", "startDate": "2021-12-31", "discountFactor": 0.7923508883940772, "ratePercent": 1.1705526921350629, "tenor": "20Y", "instruments": [ { "instrumentCode": "GBPSB6L20Y=TWEB", "value": 1.1705 } ] },
So, I understand that the 20Y zero coupon rate is 1.170552..., and it is obtained bootstrapping the TWEB swap curve (#0GBPSB6LIRS=TWEB).
In the Desktop Application, I usually use the RIC 0#GBPSBSLZ=R, whose description is "UK Pound Sterling SB 6M Libor Zero Coupon Yield Curve", to get the previous information. Here the data for 31-12-2021:
As you can see, the 20Y point of the green line is 1.343, which is far from the 1.170 obtained through the API.
Thanks in advance.
Best Answer
-
Hi @pcarrizosa ,
Please find below solution provided by the support team-
There was a blank update received for the =TWEB RICs on 12/31/2021 causing the huge difference. The same was corrected to 1.149 on Eikon. There is also another field that holds the bootstrapped values on RDP API and not the one the client is initially comparing the values with.0
Answers
-
Hi @pcarrizosa
as per your other post, a Ticket has been raised with the IPA content team at My.Refinitiv.
I have also sent the case handler your revised email address and asked them to update the ticket with the new email.
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
- 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
- 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
- 637 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
- 88 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛