Duplicate prices for called or expired instruments

It appears that the behaviour for called bonds or expired futures has changed. I have started to receive multiple duplicate values.
For example the Lloyds 13 Bond (RIC GB040862072=) which has redeemed earlier this year returned an array of duplicate prices. It appears to have returned the final trading price as a result for each date in the time period which I requested prices for. This appears to be new behaviour because previously once a bond or future expired a null response was received.
Please can you advise what the correct behaviour should be so that I can adjust my error handling accordingly.
Request:
Request:{'Entity': {'E': 'DataGrid_StandardAsync', 'W': {'requests': [{'instruments': ['GB040862072='], 'fields': [{'name': 'TR.BIDPRICE'}, {'name': 'TR.BIDPRICE.date'}], 'parameters': {'SDate': '2022-02-03', 'EDate': '2022-04-18'}}]}}}
Response:
{"responses":[{"columnHeadersCount":1,"data":[["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"],["GB040862072=",166.5,"2022-02-02T00:00:00Z"]],"headerOrientation":"horizontal","headers":[[{"displayName":"Instrument"},{"displayName":"Bid Price","field":"TR.BIDPRICE"},{"displayName":"Date","field":"TR.BIDPRICE.DATE"}]],"rowHeadersCount":1,"totalColumnsCount":3,"totalRowsCount":55}]}
The requests were send using the Python Eikon API module.
Best Answer
-
Hi @gwade ,
according to case number 11151091
A change was made to the existing behavior, which was considered a product enhancement and it was done to make the behavior consistent with other content sets.
In case you have any further questions regarding the product, please feel free to contact the Eikon support team directly via MyRefinitiv.
0
Answers
-
hi @gwade ,
This forum is more for programming-type queries, rather than content queries such as this one. I would recommend you to contact the Eikon support team directly via MyRefinitiv.
However, for this case, case number 11151091 has been raised to a content specialist team to clarify the content. I'll keep you updated
Hope this could help
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
- 616 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 中文论坛