Guides
  1. documentation

Pagination

List endpoints under api.vibe.co use offset-based pagination via the limit and offset query parameters. The contract is the same across every list endpoint. ##

Parameters

ParameterTypeDefaultDescription
limitinteger20Maximum number of items to return in a single response. Max: 5000
offsetinteger0Number of items to skip before returning results.

Example

# First page
curl "https://api.vibe.co/campaigns?limit=50&offset=0" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "X-Vibe-Revision: 2026-05"

# Second page
curl "https://api.vibe.co/campaigns?limit=50&offset=50" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "X-Vibe-Revision: 2026-05"

Response shape

*[Verify with platform owner: the exact response wrapper. Possible shapes in use across the API are:

  • { "data": [ ... ], "pagination": { "total": N, "limit": L, "offset": O } }
  • A bare JSON array [ ... ] with pagination metadata in response headers. Confirm which is canonical and update this section accordingly.]*

What pagination does not do

  • No cursor-based pagination. List endpoints use limit and offset only.
  • Order is stable within a request but not guaranteed across requests if the underlying data changes (e.g., a new campaign created mid-pagination may appear or shift). For consistent snapshots, filter by a created_at upper bound.