List portfolio transactions

Lists account portfolio transactions with optional filters for type, asset, status, transaction ID, originating reference, time range, and sort direction. Results are cursor-paginated. Results are ordered newest first by default; set sort_direction=asc for oldest first. Page tokens are valid for up to 24 hours. A page can contain fewer than page_size matching transactions, including no transactions, while still returning next_page_token; continue until the token is absent.

Transactions can appear asynchronously. To discover new activity, poll this operation with the applicable types filters and an appropriate time range, omitting statuses or including in_progress while a transaction is being processed. For a transfer created by POST /v1/transfers, use types=transfer and the from account from the create request. For an accepted derivatives transfer created by POST /v1/accounts/{account_id}/transfers/derivatives, use types=transfer and the account_id from the request path. The transfer_id returned by either create operation is the id in a reference with kind=transfer. Once the transaction appears, that reference can be submitted in references for deterministic subsequent lookup. A transfer may appear with status=in_progress before it reaches the terminal successful or failed status; filtering only by successful can therefore hide a newly materialized transfer. The first Portfolio response after a transfer is created may contain no matching transaction even when a generic transfer has status=complete or a derivatives transfer has status=accepted; continue polling until the transaction is present.

For deposits and withdrawals, reference.kind=funding identifies the originating funding transaction. For deposits, it is not the deposit destination or a payment reference from bank-transfer instructions; those values describe how to make the payment and are not accepted by references. For withdrawals, use types=withdrawal and, when the originating funding identifier is known, submit it in references as the id with kind=funding. Poll with statuses omitted until the withdrawal appears, then continue polling without that filter until its status is terminal: successful or failed. Filtering only by in_progress is useful for discovering pending withdrawals, but it excludes terminal results and must be removed or changed before polling for completion. Once a funding transaction appears, its reference can be used for deterministic subsequent lookup. The returned Portfolio transaction id uses the TX namespace and is distinct from the funding identifier in reference.id.