Skip to main content
Collection endpoints accept limit and offset query parameters.

Response shape

Paginated responses wrap results in data and paging state in metadata:
next and prev are paths, not absolute URLs — join them to the API host before requesting them.
Follow metadata.next until it is null rather than computing offsets from total_count. A collection changing underneath you can otherwise cause a page to be skipped or repeated.

Filtering

Most collection endpoints also accept filters, which combine with paging. search is a case-insensitive match over customer-facing fields; other filters are exact. See the individual endpoints under FLO API for the filters each one supports.
This envelope differs from the Nexus API, which returns a links object and an X-Total-Count header. Code written against one will not read the other.