Lipper Fund Distribution/Dividend Data

Question

Hi, my client is using WS API through the codebook. they have advised that they are unable to extract funds distributions data using the sample RICS and datatypes below. Is Lipper Data available in Codebook?

LP68378190

LP68037657

VAS.AX

IOZ.AX

"TR.FundIncDistribution;TR.FundExDate;TR.FundExDate;TR.FundRecordDate;TR.FundPayDate;TR.FundDiv;TR.FundDivCurr"

Jirapongse · Answer

@PhiloCapital

I got the same error when using the platform session.

To the best of my knowledge, data distribution licenses differ between desktop and platform sessions. Certain data may be accessible through a desktop session but not permitted for use via a platform session.

The moderators of this forum are unable to assist with permission or account-related issues. Please contact your LSEG account or sales team directly to verify your specific use case.

PhiloCapital · Answer

Thanks @ujjawal_khandelwal — that's helpful, and it confirms the data and field recipe are valid. But I think the library is a red herring for our case, and I want to give you the detail to narrow it down.

We're not using the Eikon library. Our pipeline runs the LSEG Data Library, and to be sure I just re-tested under `lseg.data` 2.1.1 (your suggested library) as well as `refinitiv.data` 1.6.2 — same result on both.

The key difference is the session type. Your snippet uses `ld.open_session()` with no arguments, which opens a desktop session inside Codebook/Workspace and inherits the signed-in Workspace user's entitlements — so it succeeds. Our pipeline is a headless service and authenticates with a platform session (machine login via `GrantPassword`, `signon_control=True`). Running your exact call on that platform session:

import lseg.data as ld

from lseg.data.session import platform

session = platform.Definition(

  app_key=APP_KEY,

  grant=platform.GrantPassword(username=SERVICE_ACCOUNT, password=PASSWORD),

  signon_control=True,

).get_session()

session.open()

ld.session.set_default(session)

ld.get_data(

  universe=['LP68037657'],   # your RIC

fields='TR.FundIncDistribution;TR.FundExDate;TR.FundRecordDate;TR.FundPayDate;TR.FundDiv;TR.FundDivCurr')

returns:

LDError: The access to field(s) denied.

Requested universes: ['LP68037657']. Requested fields: ['TR.FUNDINCDISTRIBUTION;...;TR.FUNDDIVCURR']

This is an entitlement denial (error 221), not a code or library issue — every `TR.Fund*` field is denied on this account, down to a single plain field like `TR.FundCurrency`. Importantly, we can retrieve these exact `TR.Fund*` fields without any problem on our own desktop/Workspace session — the same fields and RICs return data there, just as they did for you. So the content is clearly entitled to our organisation at the desktop level; it has simply not been extended to the headless platform service account the script uses.

Is the Lipper fund distribution content (`TR.Fund*`) entitled for our platform/machine login, and if not, what's required to enable it on that account? Could you reproduce against a platform session (rather than desktop/Codebook), and/or check the entitlements on our service account?

ujjawal_khandelwal · Answer

Hi @Will_J_H,

Thank you for reaching out!

To better understand what might be going wrong on the client side, it would be helpful to review the code they are currently using.

In the meantime, I ran a simple test on my end and was able to retrieve the data successfully.

Since the question was posted under the “Eikon Data APIs” category, I assume the user is working with the Eikon library. Please note that this library is now obsolete, and I would recommend transitioning to the LSEG Data Library for Python, which is the supported and actively maintained option.

Below is a sample code snippet using the LSEG Data Library:

import lseg.data as ld

ld.close_session()

ld.open_session()

ld.get_data(

    universe=['LP68037657'],

    fields='TR.FundIncDistribution;TR.FundExDate;TR.FundExDate;TR.FundRecordDate;TR.FundPayDate;TR.FundDiv;TR.FundDivCurr'

)

This might be helpful too: Upgrade from using Eikon Data API to the Data library | Devportal

Please let me know if this helps or if you’d like further assistance.

Thank you : )

EXPLORE OUR SITES