## Filter Terminals

Returns a paginated list of terminals for the authenticated merchant with search capabilities.

This endpoint provides full-text search functionality using the SearchIndex infrastructure,
allowing you to search terminals by name, external ID, and branch name.

## Endpoint signature

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

{
  per_page: number?,
  page: number?,
  terms: string?,
}
```

Returns: object

## Request arguments

### `per_page` (number)

_Optional_. Number of terminals 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 terminal content. Searches terminal name, external ID, and branch name. Uses fuzzy matching for partial text matches.

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