# Pagination and filtering

Sales Layer APIs support query parameters to control which records are returned and how much data each response contains.

The exact parameters depend on the API and endpoint. The OpenAPI reference is the source of truth for each operation.

## Query parameter guide

| Parameter | Purpose | Guide |
|  --- | --- | --- |
| `$select` | Choose specific fields in Catalog responses. | [Select](/guides/select) |
| `$filter` | Filter records by supported properties. | [Filter](/guides/filter) |
| `$orderby` | Sort returned records. | [Orderby](/guides/orderby) |
| `$expand` | Include supported embedded Catalog collections. | [Expand](/guides/expand) |
| `$top` | Limit page size. | [Page size limits](/guides/page-size-limits) |
| `$skip` | Skip a number of records for offset pagination. | [Pagination strategies](/guides/pagination-strategies) |
| `$skipToken` | Continue pagination from a token when supported. | [Pagination strategies](/guides/pagination-strategies) |


## Supported by API

| API | Documented query parameters |
|  --- | --- |
| DAM REST API | `$filter`, `$orderby`, `$top`, `$skip` |
| Catalog REST API | `$select`, `$expand`, `$filter`, `$orderby`, `$top`, `$skip`, `$skipToken` |


## Recommendations

* Request only the fields and records needed by the integration.
* Use metadata endpoints to discover Catalog fields.
* Keep page sizes reasonable.
* Apply filters before processing data client-side.
* Use stable sorting for repeatable pagination.
* Handle empty result sets as valid responses.