Skip to content
FacilydevelopersDashboard
Build with Facily
DocsREST APIsPagination and filtering
Search the full API reference Esc to close

Pagination and filtering

Walk large result sets with opaque cursors and resource-specific filters.

Get support

Walk a list with cursors

Omit cursor on the first request. Read the returned pagination, then send the opaque cursor unchanged on the next request. Stop when has_more is false.

Request paths
GET /v1/facilities/{facility_id}/tenants?limit=50
GET /v1/facilities/{facility_id}/tenants?limit=50&cursor=<URL_ENCODED_CURSOR>

The default limit is generally 50 and the maximum 200. Check each endpoint’s query schema for its exact bounds. total_count can be null on later pages; retain the first-page count when appropriate.

Filtering and sorting

Filters are resource-specific. Use the parameters listed on the endpoint, preserve the same filters during a cursor walk, and URL-encode query values. A search parameter is supported only where documented.

Facility-scoped list routes that explicitly support all can aggregate accessible facilities for a caller with organization-level read permission. It is case-sensitive and is not a substitute for a UUID in mutations or detail routes.

Jump to a numbered page

Some list endpoints also support a 1-based page query. Never send page and cursor together. Numbered pages can shift under concurrent writes, so prefer cursors when walking a dataset.

The offset is bounded at 100,000 rows. Add a filter or use cursor pagination for older records. Endpoints without a documented page parameter do not support numbered jumps.

Build something that works beautifully.

Facily API · Contract v1.200 · Reviewed October 29, 2026

Pagination and filtering | Facily Developers