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
- 6 AHS
- 39 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
- 368 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛