## Filter Payment Links

Returns a paginated list of payment links for the authenticated merchant with advanced filtering capabilities.

This endpoint provides comprehensive search functionality using database-driven filtering,
allowing you to filter links by status, amount ranges, and date ranges.

The response includes pagination controls with `previous` and `next` cursors that can be used
to navigate through the payment link history efficiently.

### Features:
- **Full-text search**: Search across payment link descriptions and UIDs
- **Advanced filtering**: Filter by status (active, disabled, expired, paid)
- **Range support**: Support for amount ranges and date ranges

## Endpoint signature

```http
POST https://api.reservepay.com/merchants/filter-payment-links HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>

{
  per_page: number?,
  page: number?,
  terms: string?,
  status: string?,
  amount: string?,
  created_at: string?,
  expires_at: string?,
}
```

Returns: object

## Request arguments

### `per_page` (number)

_Optional_. Number of payment links to return per page. Default: 10, Maximum: 100

### `page` (number)

_Optional_. Page number for pagination. Default: 1 (first page)

### `terms` (string)

_Optional_. Full-text search across payment link descriptions and UIDs. Uses fuzzy matching for partial text matches.

### `status` (string)

_Optional_. Filter by status (active, disabled, expired, paid)

Allowed values:

- `ACTIVE`
- `DISABLED`
- `EXPIRED`
- `PAID`

### `amount` (string)

_Optional_. Filter by amount. Supports: exact amount (1000), range (1000..5000), or boundless ranges (1000.. or ..5000). Amounts are in the smallest currency unit (cents for USD).

### `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`)

### `expires_at` (string)

_Optional_. Filter by expiration date. Supports: specific date (YYYY-MM-DD), date range (YYYY-MM-DD..YYYY-MM-DD), or keywords.

## Response attributes

### `previous` (object)

_Nullable_. 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.

### `page` (array)

**Always present**. The current page of records, ordered by creation date (newest first). Each record is serialized according to the specified record_serializer option.

### `next` (object)

_Nullable_. 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.

## Errors common to all endpoints

### `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.