# FAQs

## Frequently Asked Questions

<details>

<summary>Do requests need to be paginated?</summary>

No, the Sesame Data APIs are unpaginated, meaning all data is returned in a single response.

</details>

<details>

<summary>How are NULL fields handled in the response?</summary>

NULL results which are part of a response element are not returned. Certain fields are mandatory. See [API Endpoints](https://docs.landytech.com/sesame-data-v2/api-endpoints).

</details>

<details>

<summary>How do I know which portfolio each bank account's data is being stored in?</summary>

In the `entities` endpoint, the `PORTFOLIO.CODE` field connects the portfolio to the identifier used by banks, brokers and custodians to identify each bank account.

</details>

<details>

<summary>Do you separate different asset types between endpoints?</summary>

No. All positions (regardless of the underlying asset type) are found in the `/positions` endpoint. Similarly, all transactions (regardless of the underlying asset type) are all found in the `/transactions` endpoint.

</details>

<details>

<summary>How are cash transactions and positions treated?</summary>

Like any other asset or liability, different currencies have their own `ASSET.ID`, and any positions or transactions on these will be available via those endpoints.

</details>

<details>

<summary>Why does the <code>/positions</code> endpoint have sub portfolio information?</summary>

Where a feed shares this granularoty, on a given date, the sub portfolio data decomposes a single cash position into multiple cash balances per SUB\_PORTFOLIO\_CODE. SUB\_PORTFOLIO\_CODE can also be referred to as broker code or broker account code. In `POSITION.MARKET_VALUE_LOCAL`, these cash positions in the same currency are aggregated in a single balance.

`POSITION.GRANULARITY` > `SUB_PORTFOLIO` > `SUB_PORTFOLIO_CODE` is distinct per position.

</details>

<details>

<summary>How do you handle transactions which are reversals of previous transactions?</summary>

In the `/transactions` endpoint, the `TRANSACTION.REVERSAL` field will indicate if a transaction is a reversal by way of a true/false flag. Where true, the directions of fields like `TRANSACTION.MOVEMENT_LOCAL` and `TRANSACTION.MOVEMENT_REPORTING` will be opposite to those from the original transaction. Where available, the field `TRANSACTION.CUSTODIAN_REVERSED_TRANSACTION_ID` will link the reversal and original transactions.

</details>

<details>

<summary>What if I have a query about the data returned in the response, or the data does not reflect what is in my bank statement?</summary>

Use the Sesame support chat, and provide the cURL of your request.

</details>

<details>

<summary>What if I have an error message that I cannot resolve?</summary>

Use the Sesame support chat, and provide the cURL of your request.

</details>