The dividend is due to be paid on the 1st of December (it is under dividend type: forecast interim), hence, you would need to slightly change your request in order to get it.
Firstly, the fields that you would need to use, are under Content Classification > Corporate Actions > Dividend History in DIB.
Secondly, in the request params you will need to set something like this:
"SDate=3M EDate=-1Y DivType=66:65:60:61" (Interim, Final, Forecast Interim, Forecast final)
Thirdly, in order to use the fields from DIB in COM, you will need to activate your DEX API a little bit differently as described here.
Dividends returning old values for some stocks

I'm using the Eikon API for .NET, and for some stocks I request dividend pay dates and ex dates and they're old.
For example, 8369.T (Bank of Kyoto Ltd), I used the field names RCA.DH.ExDate and RCA.DH.PayDate and they respectively give me March 29 2017 and June 30 2017 despite the dividend that happened Sept 27. I am using the wrong fields? Why is it some stocks and not others?
I noticed in DIB in Eikon that the fields DIVPAYDATE and EXDIVDATE are correct but when I try to request them I get back that they are not valid request parameters.
Best Answer
-
The dividend is due to be paid on the 1st of December (it is under dividend type: forecast interim), hence, you would need to slightly change your request in order to get it.
Firstly, the fields that you would need to use, are under Content Classification > Corporate Actions > Dividend History in DIB.
Secondly, in the request params you will need to set something like this:
"SDate=3M EDate=-1Y DivType=66:65:60:61" (Interim, Final, Forecast Interim, Forecast final)
Thirdly, in order to use the fields from DIB in COM, you will need to activate your DEX API a little bit differently as described here.
0
Answers
-
So can I use the fields I was using before (RCA.DH.ExDate and RCA.DH.PayDate) with the request parameters you describe here?
0 -
No, you cannot. It would be best to migrate to Eikon 4 field naming scheme, as at this point there's no good way to discover metadata for Eikon 3 field naming scheme, especially for the parameters you can use, as I explained on another thread.
https://community.developers.refinitiv.com/questions/20499/list-of-eikon-v3-fields.html0
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
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 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
- 276 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
- 669 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
- 229 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
- 48 中文论坛