Developer reference

Pagination

Read bounded pages, inspect endpoint metadata and avoid treating partial history as a complete export.

Pagination limits how much a request returns. Each list has its own query contract; do not assume all endpoints accept the same filters or cursors.

Transaction pages

GET /api/v1/v2/transactions accepts page and page_size. The maximum page size is 100.


GET /api/v1/v2/transactions?page=1&page_size=25
Accept: application/json
Authorization: Bearer YOUR_HELM_API_TOKEN

Inspect returned pagination metadata to decide whether another page exists. Do not describe page one as all transactions.

Traversing changing data

Use stable record IDs to deduplicate. New records may appear while you traverse pages, so a series of paginated reads is not necessarily a frozen export snapshot. Preserve the dates and ordering semantics actually supplied by the endpoint.

Messages and imports

Stored SMS and import-job rows have their own contracts. The first-party stored-message picker displays pages of 20 and preserves selection across them. Your integration should inspect the intended job/row endpoint rather than reuse transaction parameters by assumption.

Product boundary

Advanced Activity search, filtering and complete-history export are planned. The reserved export scope does not turn list pagination into a supported full export facility.

Consult registered endpoints and integration examples for the intended read patterns.