Upgrade from Eikon -> Workspace. Learn about programming differences.
For a deeper look into our Eikon Data API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
I have issue only when requesting this particular fund LU0855227368
its related to lipper api
https://api.refinitiv.com/data/funds/v1/assets
{'request': '80005475-0000-f400-b63f-84710c7967bb#PRD2-205', 'date': '2022-10-10T15:00', 'code': '500', 'status': 'Internal Server Error Occured', 'message': 'Invalid currency: Specified currency cannot be used to call this method.\r\n\r\n [c365a4c378824742af60c81ae38a3560]'}
Please be informed that this question has been moved to Refinitiv Data Platform forum
Thanks,
AHS
hi @maximilian.mayrl ,
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
Please be informed that this is solved, as mentioned in case number 11685861 below
We are now able to call with successful response using below API endpoint on Holdings information for ISIN LU0855227368 https://api.refinitiv.com/data/funds/v1/assets?symbols=LU0855227368&properties=Holdings[start:2022-01-01%3Bend:2022-10-12]
Hi @maximilian.mayrl ,
Regarding an error message, seems like the currency used is not supported by this endpoint. Could you please provide the request body you used so we could check the currency in the request?
Hi, @raksina.samasiri Did that information help you? Here is some additional information:
Only additional information we send is the Authorization token as header.
Hi @maximilian.mayrl ,
Thank you for your patience. First, I'd like to inform you that this is being investigated by the support team as I found the same issue in case number 11685861 raised by a user from the same company as yours.
As this is a technical issue, the support team has been investigating it and will contact the user directly regarding the investigation result and the suggestion for the fix.
I'll also keep you updated.
