Pagination

Cursor-based pagination

All list endpoints return paginated results. The response includes a next_cursor field; pass it as the cursor query parameter on the next call to fetch the next page.

# First page
GET /v1/inbox/comments?limit=25

# Next page (use next_cursor from previous response)
GET /v1/inbox/comments?limit=25&cursor=eyJpZCI6IjE3ODQx...

When there are no more results, the response omits next_cursor (or returns it as an empty string). This pattern applies to all list endpoints: /v1/inbox/comments, /v1/inbox/conversations, /v1/inbox/reviews, /v1/posts, /v1/media, and others.

Filtering

Most list endpoints support filtering parameters. For example:

# Posts with comments, filtered by account and platform
GET /v1/inbox/comments?account_id=acc_01HZ...&platform=instagram&limit=25

# Published posts, sorted by date descending
GET /v1/posts?status=published&sort=created_desc&limit=25

See the API Reference for the full set of query parameters on each endpoint.

Parameters

Parameter	Type	Default	Description
`limit`	integer	varies	Results per page. Min 1, max 100. Default varies by endpoint: most endpoints default to 25, the shared validator defaults to 20, `/v1/media` defaults to 50, and `/v1/inbox/comments/{postId}/{commentId}/replies` defaults to 10.
`cursor`	string	-	Opaque pagination cursor from the previous response’s `next_cursor` field.

Getting Started

Core Concepts

Filtering

Parameters

​Cursor-based pagination

​Filtering

​Parameters

Cursor-based pagination

Filtering

Parameters