GET
/transactionsAPIAuthentication:Bearer token
Authorization: Bearer <token>Security requirement: 403 CSRF Protection
Direct server-to-server calls authenticated via Bearer tokens do not require CSRF headers. If you instead invoke mutation endpoints from a web browser using cookie-based sessions, you must include the following header:
X-Requested-With: XMLHttpRequestQuery params
| Field | Type | Required | Description |
|---|---|---|---|
page | number | Optional | Page number. Defaults to 1. |
limit | number | Optional | Page size. Defaults to 100. Maximum 100. |
sort | string | Optional | Comma-separated fields: id, amount, method, status, createdAt. Prefix - for descending. Default is -createdAt. |
fields | string | Optional | Comma-separated subset of id, userId, orderId, amount, method, status, createdAt. |
status | string | Optional | Exact status filter. |
method | string | Optional | Exact method filter. |
amount | number | Optional | Exact amount, or amount[gte], amount[gt], amount[lte], amount[lt]. |
Response fields
| Field | Type | Presence | Description |
|---|---|---|---|
status | string | Always returned | success |
results | number | Always returned | Number of payments in this page. |
data.payments | array | Always returned | Payment rows. There is no total or next cursor. |
Status codes
| HTTP Status | Meaning |
|---|---|
| 200 | Page of payments. |
| 401 | No merchant session. |
Notes
- A userId query value is ignored. Results stay limited to the signed-in merchant.