Retrieve worker transaction history
Use this endpoint to access a worker’s transaction history quickly. This integration works with white-label clients and ensures compliance by not following the generic contractor route
Token scopes: worker:read
Authentication
Query parameters
Maximum number of transactions to return in this page (page size).
Subset of transactions by processing state. Public enum is UPPER_SNAKE; the server lowercases for validation (legacy lowercase query values are still accepted).
Lower bound on transaction created_at (inclusive), ISO-8601 date-time.
Upper bound on transaction created_at (inclusive), ISO-8601 date-time.
Opaque pagination cursor from the previous response field next_cursor. Omit on the first page; pass the last next_cursor value as cursor to fetch the next page.
Filter listed transactions to these mapped status values (applied after fetch; may affect how rows align with total_count).
Restrict to pay-in or pay-out. Public enum is UPPER_SNAKE; the server lowercases for validation (legacy lowercase query values are still accepted).
Filter by withdrawal / payout method identifiers.
Additional transaction type filter (backend-specific string).
Response
Successful operation — paginated contractor transactions.
Total number of transactions matching server-side filters for this request (ignores pagination). If statuses is provided, that filter is applied in memory to listed rows only, so this count may be higher than the rows returned across all pages.
Opaque cursor for the next page; null when there is no next page. Pass this value as the cursor query parameter to request the following page.