Skip to main content
GET
List Transactions
Cursor-paginated list of transactions. Subject resolution intentionally NOT via 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

Authorization
string
header
required

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

external_ref
string | null

Filter to a single partner-user. Omit to query all Connect-provisioned users for this tenant.

type
string | null

Comma-separated. Allowed: deposit, payout, transfer, conversion (Phase 4), ramp (Phase 4).

status
string | null

Comma-separated. Allowed: pending, confirmed, failed.

from
string | null

Inclusive lower bound on created_at (ISO 8601).

to
string | null

Inclusive upper bound on created_at (ISO 8601).

cursor
string | null

Opaque continuation token from a previous response's cursor field. Omit to fetch the first page.

limit
integer
default:50

Max rows to return (clamped to 200).

Required range: 1 <= x <= 200

Response

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).

has_more
boolean
required

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.

data
ConnectTransactionLine · object[]
cursor
string | null

Pass this back as ?cursor=... to fetch the next page. None on the last page.