How to get full holdings for a fund via DSS Rest API

We use the following example request given in the file below
We expected that we get the instruments where the fund is invested in together with some additional information like the value in the fund invested amount.
Unfortunately this seems to be the wrong request type since we just get information about the fund itself and not its holdings.
Could you give us an example request for getting the holdings of a fund?
Best Answer
-
Here is the query for ISIN
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.FundAllocationExtractionRequest",
"ContentFieldNames": [
"Asset SubType Description",
"Asset Type",
"Asset Type Description",
"CUSIP",
"Identifier Segment Source",
"Identifier Segment Source Description",
"Instrument ID",
"Instrument ID Type",
"Security Description",
"Allocation Asset Type",
"Allocation CUSIP",
"Allocation Date",
"Allocation Item",
"Allocation OrgID",
"Allocation Percentage",
"Allocation Rank",
"Market Value Currency",
"Market Value Held",
"RIC",
"FundSERVAC",
"FundSERVBE",
"FundSERVDM",
"FundSERVDO",
"FundSERVFE",
"FundSERVIS",
"FundSERVLL",
"FundSERVNL",
"FundSERVVS"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "DE0005317333",
"IdentifierType": "Isin"
}
],
"ValidationOptions": null,
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"FundAllocationTypes": [
"Asset",
"Currency",
"FullHoldings",
"IndustrySector",
"InvestmentCountry",
"TopTenHoldings"
]
}
}
}0
Answers
-
Hello @rahul.deshmukh,
I think the request for fund holdings is the right request. However, the RIC identifier has to be a Lipper RIC in order to request funds holdings info, and I expect one has to be entitled for the relevant content set. This request works for me:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.FundAllocationExtractionRequest",
"ContentFieldNames": [
"Asset SubType Description",
"Asset Type",
"Asset Type Description",
"CUSIP",
"Identifier Segment Source",
"Identifier Segment Source Description",
"Instrument ID",
"Instrument ID Type",
"Security Description",
"Allocation Asset Type",
"Allocation CUSIP",
"Allocation Date",
"Allocation Item",
"Allocation OrgID",
"Allocation Percentage",
"Allocation Rank",
"Market Value Currency",
"Market Value Held",
"RIC"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "LP68233262",
"IdentifierType": "Ric"
}
],
"ValidationOptions": null,
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"FundAllocationTypes": [
"Currency",
"FullHoldings"
]
}
}
}However, for a definitive answer on how to request specific content correctly, in terms of identifiers needed, for a customer, a much better resource would be Refinitiv Content Helpdesk Online , select DSS + "I need help finding content".
0 -
Try this:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.FundAllocationExtractionRequest",
"ContentFieldNames": [
"Asset SubType Description",
"Asset Type",
"Asset Type Description",
"CUSIP",
"Identifier Segment Source",
"Identifier Segment Source Description",
"Instrument ID",
"Instrument ID Type",
"Security Description",
"Allocation Asset Type",
"Allocation CUSIP",
"Allocation Date",
"Allocation Item",
"Allocation OrgID",
"Allocation Percentage",
"Allocation Rank",
"Market Value Currency",
"Market Value Held",
"RIC",
"FundSERVAC",
"FundSERVBE",
"FundSERVDM",
"FundSERVDO",
"FundSERVFE",
"FundSERVIS",
"FundSERVLL",
"FundSERVNL",
"FundSERVVS"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "LP60054179",
"IdentifierType": "Ric"
}
],
"ValidationOptions": null,
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"FundAllocationTypes": [
"Asset",
"Currency",
"FullHoldings",
"IndustrySector",
"InvestmentCountry",
"TopTenHoldings"
]
}
}
}result:
Mutual Funds,MTLF,Mutual Funds,,F,Mutual Fund,LP60054179,RIC,HannoverscheMaxInvest,,,2020/04/30,CASH,,3.53,2,,,LP60054179,,,,,,,,,
Mutual Funds,MTLF,Mutual Funds,,F,Mutual Fund,LP60054179,RIC,HannoverscheMaxInvest,,,2020/04/30,FRANCE,,35.11,1,,,LP60054179,,,,,,,,,
Mutual Funds,MTLF,Mutual Funds,,F,Mutual Fund,LP60054179,RIC,HannoverscheMaxInvest,,,2020/04/30,GERMANY,,27.86,2,,,LP60054179,,,,,,,,,0 -
extraction_request_ISIN.txtHello @Zoya.Farberov,
Unfortunately this request doesn't provide the identifier information for ISIN which we actually need to get the funds holdings info. When i tried to provide "IdentifierType":ISIN then i am getting the response as 'Bad Request'
Can you please provide the request type where Identifier should be ISIN to get the funds holdings info?
Thanks.
0 -
Hallo Gurpreet,
Unfortunately this request doesn't provide the identifier information for ISIN which we actually need to get the funds holdings info. When i tried to provide "IdentifierType":ISIN then i am getting the response as 'Bad Request'
Can you please provide the request type where Identifier should be ISIN to get the funds holdings info?
Regards.
0 -
Hallo Gurpreet,
Currently i am facing performance issue as i am trying to process http request one per ISIN.
Do you have an example where we can process multiple ISIN per http request ? Also any other example may be using threading or other approach to improve performance ?
Thanks and regards,
Rahul Deshmukh
0 -
PS: Please ask new questions in a new post. It helps us track responses.
You can specify more than one instrument in a single request, since InstrumentIdentifiers is a JSON array. Example:
"InstrumentIdentifiers": [{
"Identifier": "SHV.O",
"IdentifierType": "Ric"
}, {
"Identifier": "00209tab1",
"IdentifierType": "Cusip"
}, {
"Identifier": "IBM.N",
"IdentifierType": "Ric"
}, {
"Identifier": "US4592001014",
"IdentifierType": "Isin"
}, {
"Identifier": "B1YW440",
"IdentifierType": "Sedol"
}
]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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛