> For the complete documentation index, see [llms.txt](https://docs.landytech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.landytech.com/api-endpoints/holdings.md).

# Holdings

The `holdings` endpoint contains the holdings (or positions) of your entities. For each date where holdings are received from a custodian, data will be available in the holdings endpoint once standardised through the data processing layer. Requests are made using the `entityId` parameter, which is mandatory. 

For the full list of parameters accepted as well as which are required, see `Parameters` below. To view Sample response data, expand the menu under `Responses` and refer to the `Example` tab. To see the format of the response fields, as well as which are mandatory (that is, always returned in the response), select the tab `Schema`, and then expand `object` followed by `content` and finally `object` once more. 

## Request and Response

{% hint style="info" %}
You might find it helpful to access our [Sesame Data Developer Portal](/sesame-data-developer-portal.md)
{% endhint %}

The format of all Sesame Custodial Data APIs is the same. The user is required to provide their account UUID and token in the authorisation, and then make a `GET` request to the `holdings` endpoint, specifying the entityId of the entity being requested.\
\
In the response, the results of shown per holding, which is an asset held on a date. All results within that JSON level (for example, quantity, unit price) pertain to that holding.

{% openapi src="/files/Op9p4eG621woDfclloBE" path="/api/v1/holdings/{entityId}" method="get" expanded="true" %}
[openapi\_114\_06Jun25.yaml](https://686422464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRqYhxcZf6UoirhKFZnW4%2Fuploads%2Fl8kOz8iaZGcmfcJzGmQz%2Fopenapi_114_06Jun25.yaml?alt=media\&token=d7c18101-35d7-4f9d-b950-e2a3b428bd2a)
{% endopenapi %}