List Operations
OpenAPI SpecDeprecated
Test this endpoint live
Open the same request directly in API Explorer.
Server URL
Deprecated — use V2
Do not use this endpoint for new integrations. V1 is deprecated and will reach end of life soon. New integrations must use List Operations V2. Existing integrations should migrate to V2 as soon as possible.
Retrieve a paginated list of transaction operations.
Query parameters page and perPage can be used to control pagination. finalizedBefore and finalizedAfter can be sent to only get operations finalized between certain timeframes. pointOfSaleId can be used to limit the operations to a list of points of sale.
The endpoint only returns operations in a finalized state of FAILED or SUCCESS.
Page number.
1Number of items per page.
value <= 50025A filter to limit operations created finalized before a certain time. RFC 3339 format.
date-timeA filter to limit operations created finalized after a certain time. RFC 3339 format.
date-timeAn optional filter to limit operations from the given points of sale.
Response Body
application/json
application/json
application/json
application/json
List Operations V2
Retrieve finalized transaction operations for the authenticated merchant using cursor-based pagination. Only operations in a final state of SUCCESS or FAILED are returned. Results are ordered by operation ID in descending order, not by finalization time. Omit offset for the first page. While hasMore is true, pass the returned nextOffset as offset to retrieve the next page, keeping the same filters. Stop when hasMore is false; a non-empty last page can still contain a nextOffset value. Combine operation types, a final state, transaction IDs, points of sale, and an inclusive finalization-time window to narrow the results. Values within each list are matched with OR; different filters are combined with AND. For example, type=CAPTURE&type=REFUND&state=SUCCESS returns successful captures and refunds. Migrating from V1: replace page with offset and use hasMore to determine whether to continue. Each entry in items now contains an operation object. Page numbers, totals, and pagination URLs are not returned. Unlike V1, the order follows operation IDs rather than finalizedAt.
Payout (Asynchronous)
Initiate an asynchronous payout to send funds to a cardholder. A webhook will be sent to the specified notificationUrl once processed. We recommend a minimum timeout of 5 seconds.