List Transactions
Cursor-paginated list of transactions.
resolve_subject
because that dependency would translate the external_ref
into an internal user_id here, but the service does its
own filtering via the connect_external_refs join — keeping the
raw string forwarded means the service decides whether the ref
exists or just returns an empty page (correct UX for unknown
refs).Authorizations
Paste your Connect API key (sk_live_… for production, sk_test_… for sandbox) without the Bearer prefix. Mint and rotate keys from the admin panel.
Query Parameters
Filter to a single partner-user. Omit to query all Connect-provisioned users for this tenant.
Comma-separated. Allowed: deposit, payout, transfer, conversion (Phase 4), ramp (Phase 4).
Comma-separated. Allowed: pending, confirmed, failed.
Inclusive lower bound on created_at (ISO 8601).
Inclusive upper bound on created_at (ISO 8601).
Opaque continuation token from a previous response's cursor field. Omit to fetch the first page.
Max rows to return (clamped to 200).
1 <= x <= 200Response
Successful Response
Paginated list response.
cursor is the opaque continuation token for the next page;
None on the last page. has_more is the boolean partners
actually loop on (some clients find that easier than checking
cursor != null).
True iff at least one more row exists past this page. Computed by fetching limit + 1 rows server-side; if the SQL returns limit + 1, we slice to limit and set has_more=True.
Pass this back as ?cursor=... to fetch the next page. None on the last page.