Tablewealth

Pagination

Page through API list responses with pageSize and pageToken.

List endpoints use cursor-style pagination. Use pagination for accounts, transactions, holdings, and account-scoped child lists.

Request parameters

List endpoints accept pageSize and pageToken.

pageSize

pageSize controls how many records the API should return in the current page. The maximum page size is 100.

pageToken

pageToken resumes a list request from the previous response. Pass pagination.nextPageToken unchanged.

Response shape

List responses include a pagination object.

{
  "data": [],
  "pagination": {
    "pageSize": 50,
    "nextPageToken": "..."
  },
  "meta": {}
}

Continue paging

If pagination.nextPageToken exists, request the next page:

curl "https://api.tablewealth.com/v1/transactions?pageSize=50&pageToken=$NEXT_PAGE_TOKEN" \
  -H "X-API-Key: $TABLEWEALTH_API_KEY"
const url = new URL('https://api.tablewealth.com/v1/transactions');
url.searchParams.set('pageSize', '50');
url.searchParams.set('pageToken', nextPageToken);

const response = await fetch(url, {
  headers: {
    'X-API-Key': process.env.TABLEWEALTH_API_KEY!
  }
});

const page = await response.json();
import os
import requests

response = requests.get(
    "https://api.tablewealth.com/v1/transactions",
    headers={"X-API-Key": os.environ["TABLEWEALTH_API_KEY"]},
    params={"pageSize": 50, "pageToken": next_page_token},
    timeout=30,
)
response.raise_for_status()
page = response.json()

Stop condition

If pagination.nextPageToken is absent, the list is complete for the current query.

Empty pages

Empty lists can mean the key has restricted account access. They do not always mean the organization has no matching data.

Common causes

  • The key is limited to selected accounts.
  • The selected accounts do not support the requested resource.
  • Date filters exclude the available records.
  • The key lacks the required scope.

On this page