-
- Abort payment on terminal
- Capture payment
- Filter payments
- Find payment
- Initiate payment flow
- List payment activities
- List payments
- List payments by contact
- List payments by terminal
- Refund payment
- Request payment
- Resume payment on terminal
- Retrieve refund performance
- Retrieve sales performance
- Reverse payment
- Start payment on terminal
- Void payment
Filter Contacts
Returns a paginated list of contacts for the authenticated merchant with filtering capabilities.
Filter by name, email, mobile (substring match) and creation date. Free-text terms also matches contact ID and external ID.
Results are ordered by creation date descending.
per_page
number
Optional. Number of contacts to return per page. Default: 10, Maximum: 100
page
number
Optional. Page number for pagination. Default: 1 (first page)
name
string
Optional. Filter by contact name (substring, case-insensitive).
email
string
Optional. Filter by contact email (substring, case-insensitive).
mobile
string
Optional. Filter by contact mobile (substring).
terms
string
Optional. Free-text search across contact name, email, mobile, contact ID, and external ID (substring, case-insensitive).
created_at
string
Optional. Filter by creation date. Supports: specific date (YYYY-MM-DD), date range (YYYY-MM-DD..YYYY-MM-DD), or keywords (today, yesterday, this_week, last_week, this_month, last_month).
| Attribute | Description |
|---|---|
previousobject
|
Pagination for the previous page. Contains 'before' (page number) and 'per_page' (page size) parameters. Use these values in the 'page' and 'per_page' parameters of the next request to get the previous page. Returns null if there is no previous page. |
pagearray
|
The current page of records, ordered by creation date (newest first). Each record is serialized according to the specified record_serializer option. |
nextobject
|
Pagination for the next page. Contains 'after' (page number) and 'per_page' (page size) parameters. Use these values in the 'page' and 'per_page' parameters of the next request to get the next page. Returns null if there is no next page. |
UNHANDLED_ERROR
This error occurs when the server encounters an unexpected internal error that it cannot handle gracefully. This typically happens due to bugs, infrastructure issues, or edge cases that weren't anticipated during development.
INVALID_ARGUMENTS
This error occurs when the request contains invalid or missing parameters. Common cases include missing required fields, or values that don't match the expected format or type.
BAD_VERSION
This error occurs when making requests to an API version that does not exist. This commonly happens when using an outdated SDK or when the API version specified in the request URL is incorrect.
