List Transactions | SQRIL

Lists transactions for the authenticated exchange app with optional filtering and pagination.

Authentication:

REQUIRED: Provide client_id and client_secret via:
Basic Auth: Authorization: Basic base64(client_id:client_secret)
The exchange_app_id is automatically derived from authenticated credentials (not accepted as query parameter)

Query Parameters:

status (optional): Filter by transaction status (PENDING, PROCESSING, SUCCESS, FAILED)
limit (optional): Number of transactions to return (1-100, default: 50)
start_after (optional): Transaction ID to start after for pagination (cursor-based pagination)
start_date (optional): Start date for date range filter (ISO 8601 format, e.g., ‘2024-01-01T00:00:00Z’). Filters transactions where created_at >= start_date
end_date (optional): End date for date range filter (ISO 8601 format, e.g., ‘2024-01-31T23:59:59Z’). Filters transactions where created_at <= end_date
detail (optional): full returns the legacy wide transaction objects (full qr_data, duplicate flat recipient columns). Default is slim (smaller payload per row).

Date Range Filtering:

Both start_date and end_date are optional and can be used independently or together
Dates must be in ISO 8601 format (e.g., ‘2024-01-01T00:00:00Z’)
If both dates are provided, start_date must be before or equal to end_date
Date range filtering is based on the transaction’s created_at timestamp
Date range can be combined with status filtering

Response:

transactions: Array of transaction objects
total: Number of transactions returned
limit: Limit used
has_more: Whether there are more transactions available
next_cursor: Transaction ID to use as start_after for next page (if has_more is true)

Note: Transactions are ordered by created_at in descending order (most recent first). When filtering by status, a composite index is required in Firestore. When filtering by date range with status, a composite index is required.

Lists transactions for the authenticated exchange app with optional filtering and pagination. **Authentication:** - **REQUIRED**: Provide client_id and client_secret via: - Basic Auth: `Authorization: Basic base64(client_id:client_secret)` - The `exchange_app_id` is automatically derived from authenticated credentials (not accepted as query parameter) **Query Parameters:** - `status` (optional): Filter by transaction status (PENDING, PROCESSING, SUCCESS, FAILED) - `limit` (optional): Number of transactions to return (1-100, default: 50) - `start_after` (optional): Transaction ID to start after for pagination (cursor-based pagination) - `start_date` (optional): Start date for date range filter (ISO 8601 format, e.g., '2024-01-01T00:00:00Z'). Filters transactions where `created_at >= start_date` - `end_date` (optional): End date for date range filter (ISO 8601 format, e.g., '2024-01-31T23:59:59Z'). Filters transactions where `created_at <= end_date` - `detail` (optional): `full` returns the legacy wide transaction objects (full `qr_data`, duplicate flat recipient columns). **Default is slim** (smaller payload per row). **Date Range Filtering:** - Both `start_date` and `end_date` are optional and can be used independently or together - Dates must be in ISO 8601 format (e.g., '2024-01-01T00:00:00Z') - If both dates are provided, `start_date` must be before or equal to `end_date` - Date range filtering is based on the transaction's `created_at` timestamp - Date range can be combined with status filtering **Response:** - `transactions`: Array of transaction objects - `total`: Number of transactions returned - `limit`: Limit used - `has_more`: Whether there are more transactions available - `next_cursor`: Transaction ID to use as start_after for next page (if has_more is true) **Note:** Transactions are ordered by `created_at` in descending order (most recent first). When filtering by status, a composite index is required in Firestore. When filtering by date range with status, a composite index is required.

Authentication

AuthorizationBasic

Basic Auth: base64(client_id:client_secret)

Query parameters

statusstringOptional

limitintegerOptional1-100

start_afterstringOptional

start_datedatetimeOptional

end_datedatetimeOptional

dpintegerOptional0-10Defaults to 2

Decimal places for monetary fields in the response (USD amounts, fees, exchange rates). Default 2, which rounds sub-cent fees to 0. Use dp=4 or higher to reconcile against exact deducted totals: at full precision amount_usd + percentage_fee + fixed_fee equals the amount deducted from your balance. Rounding is applied to the response only; all stored values and balance deductions always use full precision.

Response

transactionslist of objects

totalinteger

limitinteger

has_moreboolean

next_cursorstring or nullOptional

Errors

400

Bad Request Error

401

Unauthorized Error

Lists transactions for the authenticated exchange app with optional filtering and pagination.

Authentication:

REQUIRED: Provide client_id and client_secret via:
Basic Auth: Authorization: Basic base64(client_id:client_secret)
The exchange_app_id is automatically derived from authenticated credentials (not accepted as query parameter)

Query Parameters:

status (optional): Filter by transaction status (PENDING, PROCESSING, SUCCESS, FAILED)
limit (optional): Number of transactions to return (1-100, default: 50)
start_after (optional): Transaction ID to start after for pagination (cursor-based pagination)
start_date (optional): Start date for date range filter (ISO 8601 format, e.g., ‘2024-01-01T00:00:00Z’). Filters transactions where created_at >= start_date
end_date (optional): End date for date range filter (ISO 8601 format, e.g., ‘2024-01-31T23:59:59Z’). Filters transactions where created_at <= end_date
detail (optional): full returns the legacy wide transaction objects (full qr_data, duplicate flat recipient columns). Default is slim (smaller payload per row).

Date Range Filtering:

Both start_date and end_date are optional and can be used independently or together
Dates must be in ISO 8601 format (e.g., ‘2024-01-01T00:00:00Z’)
If both dates are provided, start_date must be before or equal to end_date
Date range filtering is based on the transaction’s created_at timestamp
Date range can be combined with status filtering

Response:

transactions: Array of transaction objects
total: Number of transactions returned
limit: Limit used
has_more: Whether there are more transactions available
next_cursor: Transaction ID to use as start_after for next page (if has_more is true)

1	{
2	"transactions": [
3	{
4	"id": "tx_1234567890_abc123",
5	"exchange_app_id": "app_123",
6	"customer_id": "{{customer_id}}",
7	"status": "SUCCESS",
8	"amount": 100000,
9	"amount_usd": 6.67,
10	"fee": 0.1,
11	"percentage_fee": 0.08,
12	"fixed_fee": 0.02,
13	"total": 6.77,
14	"currency": "IDR",
15	"country_code": "ID",
16	"sender": {
17	"name_first": "John",
18	"name_last": "Doe"
19	},
20	"recipient": {
21	"name": "MERCHANT NAME",
22	"account_no": "1234567890",
23	"bank_no": "014"
24	},
25	"created_at": "2024-01-01T00:00:00.000Z",
26	"updated_at": "2024-01-01T00:00:00.000Z"
27	}
28	],
29	"total": 1,
30	"limit": 50,
31	"has_more": false
32	}

$	curl https://stg-api.sqril.io/listTransactions \
>	-u "<username>:<password>"