The transactions endpoint returns the transactions which have occurred for a specific entity. For each valueDate where transactions are received from a custodian, data will be available in the transactions endpoint once standardised through 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

You might find it helpful to access our Sesame Data Developer Portal

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 transactions endpoint, specifying the entityId of the entity being requested.

Supported Transaction Subtypes

Last updated