Skip to main content
List endpoints accept query parameters that filter and sort the rows they return. The available filters and the set of sortable fields vary per endpoint, so always confirm the exact parameters on the relevant endpoint page.

Filtering

Common filter parameters across list endpoints:
string
Restrict to one platform — instagram or tiktok.
string
Case-insensitive substring search (for example, over an account’s username).
boolean
Filter by tracking state — active versus paused.
string
Scope results to a single account (UUID). Available where it makes sense, such as listing videos.
string
Scope accounts to a single creator (UUID).
Filters combine with AND. The response echoes the active filter and sort back in the filters envelope so you can confirm what produced the page.
Filter parameters are per-endpoint. For example, /v2/accounts also accepts category and creator_id, while /v2/videos accepts account_id. Check the endpoint page for the full list.

Date ranges

The analytics endpoints accept date-range parameters instead of the filters above. Daily endpoints take an inclusive start_date and end_date (YYYY-MM-DD), and the timeseries endpoints add a period preset (7d, 30d, 90d, or custom with explicit dates). See the analytics endpoints in the API reference for specifics.

Sorting

Sort with two parameters:
string
Field to sort by. Allowed values are a per-endpoint enum (see below).
string
default:"desc"
Sort direction — asc or desc.
Sortable fields are specific to each endpoint. For example: The endpoint page is the source of truth for each list’s allowed values — see the API reference.
A legacy sort parameter accepts a single signed string such as -added_at (leading - for descending). Prefer order_by + order_direction, which are validated as enums; if both are present, order_by wins.

Combining with pagination

Filters and sort are part of the cursor’s identity. Hold them constant across every page of a walk — a cursor reused under a different filter or sort returns 422. See Pagination.