Introduction
Welcome to Sesame Data! Sesame Data allows our clients to access their transactions and holdings data from multiple custodians in a standardised output format. With over 400 connections to custodians across the world, Sesame Data ensures that our clients do not have to build and maintain their own integrations with their custodians (or the custodians of their clients). Sesame Data supports custodial connections to banks, brokerages, investment managers, portfolio management systems and online trading platforms.
The custodians provide daily holding and transaction data directly to Sesame via feeds. Once received, Sesame Data standardizes the data from each file, allowing our clients a standard representation of transactions and holdings across all their custodians.
These Docs will guide you through how to use Sesame Data. If you still have any queries, please consult the FAQ section.
User types
Sesame Data caters to two user types based on their respective objectives.
Custodial
Custodial use-cases include clients who require access to standardised transaction and holding information from their custodians, standardised through Sesame. This is helpful for bookkeeping and accounting, as well as downstream analytics which are reliant on custodial information. Our clients include Trust companies at Fintechs.
Through the API, users can fetch Custodial data per Entity. An Entity contains the transactions and holdings of an account holder (a person, company, or trust which has an account with a custodian). Entities contain data from only one custodian. Thus, one person, company or trust will have their holdings in several entities from several custodians.
Enterprise
Enterprise use-cases include users of Sesame Enterprise who would also like access to the Sesame analytics through an API, either for storing or for usage in their own analytics tools. The Enterprise endpoints deliver data which is generated after Custodial data is loaded into Sesame, and has undergone further computations. This data gets calculated by Sesame or through our integrations with MSCI Risk Metrics and BarraOne.
An Entity is reflective of a legal entity, which is the investment fund. This will contain all positions and transactions of the fund on a consolidated basis (that is, from several custodians).
Our data endpoints also support Look-through, which, refers to whether the request should return the decomposed, or undecomposed positions in the response. Sesame can decompose or look-through assets into their constituent holdings, or it can return only the position in the parent asset.
Getting Started
The best way to get started is using the Developer Portal in Sesame. This requires a Sesame account, if you don't have one, you can book a request for a demo account.
All Sesame Data requests are made to the Sesame Production environment. Sesame Data only supports GET requests, making it safe to use the Production environment for any testing.
Follow these steps to access your data:
The first step is to Create and manage your API token
Next, learn How to Authenticate and use the token to get access to your data
Then explore our API Endpoints. We recommend starting with Entity List endpoint. This endpoint contains all entities (Legal entities, Portfolios, Groupings) that are available in your account.
You can use the endpoint Entity Dates to determine the dates for which data has been received from your custodians, and which are available for you to request following successful processing Sesame.
After you may want to start with Transactions endpoint to see your transactions per entity, and then consult Holdings for your positions.
You may also find it valuable to explore Sesame Data Developer Portal or our tutorial on Using Sesame Data with Postman.
Last updated
