---
title: "Retrieving properties from the domains of other types of entity"
slug: "retrieving-properties-from-the-domains-of-other-types-of-entity"
tags: ["cross-domain properties"]
updated: 2025-12-18T13:18:56Z
published: 2025-12-18T13:18:56Z
canonical: "support.lusid.com/retrieving-properties-from-the-domains-of-other-types-of-entity"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrieving properties from the domains of other types of entity

You can [retrieve properties for entities](/v1/docs/how-do-i-retrieve-a-property-or-derived-property-for-an-entity) of a particular type in LUSID using `Get*` and `List*` APIs specific to that entity type.

For example, you can call the [GetHoldings](https://www.lusid.com/docs/api#operation/GetHoldings) API to generate a holdings report and specify the `propertyKeys` parameter to 'decorate' any number of properties from the native `Holding` domain onto the response. A property in the `Holding` domain is one whose [underlying property type has a 3-stage key](/v1/docs/how-do-i-create-a-property-type) in the format `Holding/<scope>/<code>`.

Consider the following example using the equivalent `get_holdings` method in the Python SDK, where the syntax is easier to understand:

```python
get_holdings_response = transaction_portfolios_api.get_holdings(
    scope = "Finbourne-Examples", 
    code = "UK-Equities",
    property_keys = ["Holding/Ibor/CurrentMarketValue"],
)
```

For some entity types, you can also retrieve properties from other domains. For example, for holdings you can retrieve properties from the `Instrument` and `Portfolio` domains as well as `Holding`. Consider the following example, in which a holdings report is enriched with the friendly names of instruments and their countries of origin, and portfolio manager names:

```python
get_holdings_response = transaction_portfolios_api.get_holdings(
    scope = "Finbourne-Examples", 
    code = "UK-Equities",
    property_keys = ["Holding/Ibor/CurrentMarketValue", 
                     "Instrument/default/Name", 
                     "Instrument/Tax/Country", 
                     "Portfolio/Manager/Name"],
)
```

> [!NOTE]
> **Note**: Properties such as `Instrument/default/Name` that are in the protected `default` and `system` scopes are [system properties](/v1/docs/what-is-a-system-property). LUSID may automatically decorate relevant system properties onto `Get*` and `List*` API responses.

| **Entity type** | **Native property domain** | **Other retrievable property domains** | **Notes** |
| --- | --- | --- | --- |
| [Portfolios](/v1/docs/portfolios) | `Portfolio` | Any that support relationships. [More information](/v1/docs/retrieving-related-entities-and-their-properties). |  |
| [Portfolio groups](/v1/docs/what-is-a-portfolio-group) | `PortfolioGroup` | Any that support relationships. |  |
| [Instruments](/v1/docs/instruments) | `Instrument` | Any that support relationships. |  |
| [Holdings](/v1/docs/holdings) | `Holding` | `Instrument`, `Portfolio`, `CustodianAccount`, `LegalEntity` | Properties in the `Transaction` domain registered as [sub-holding keys](/v1/docs/how-do-i-register-sub-holding-keys-shks-with-a-portfolio) for a portfolio are automatically returned in a separate `subHoldingKeys` object on the response. |
| [Transactions](/v1/docs/transactions) | `Transaction` | `Instrument`, `Portfolio`, `LegalEntity`, `CustodianAccount` |  |
| [Constituents](/v1/docs/loading-constituents-and-rebalancing-a-reference-portfolio) | `ReferenceHolding` | `Instrument` |  |
| [Journal entry lines](/v1/docs/lusidaborjeline) |  | `Instrument`, `Transaction`, `Portfolio`, `Account`, `LegalEntity`, `CustodianAccount` | Journal entry lines do not have a property domain of their own. |
| [Custom entities](/v1/docs/extending-lusids-data-model-using-custom-entities) |  | Any that support relationships. | Custom entities do not have a property domain of their own. However, you can decorate properties from *related* entities onto custom entities. |
| [Legal entities](/v1/docs/representing-institutions-in-lusid-using-legal-entities) | `LegalEntity` | Any that support relationships. |  |
| [People](/v1/docs/representing-people-in-lusid-using-person-entities) | `Person` | Any that support relationships. |  |

To see whether a particular API supports this behavior, examine the [LUSID API documentation](https://www.lusid.com/docs/api) and look for a `propertyKeys` or similar query parameter. The explanation should state which property domains can be retrieved, in this case the [GetHoldingsWithOrders](https://www.lusid.com/docs/api#operation/GetHoldingsWithOrders) API:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/468c0cfe-17bd-4c51-8572-6207b34806fa.png)