Pagination

List endpoints such as GET /posts, GET /accounts and GET /comments use cursor pagination rather than page numbers, so results stay consistent even as new items are created between requests.

How it works

Every list response includes a cursor object:

{
  "data": [ /* ... */ ],
  "cursor": {
    "next": "eyJpZCI6InBvc3RfMDFKLi4uIn0",
    "has_more": true
  }
}

Pass cursor.next back as the cursor query parameter to get the next page. When has_more is false, there is no further cursor value to follow.

curl "https://api.getimma.com/v1/posts?profile_id=prof_01J...&cursor=eyJpZCI6InBvc3RfMDFKLi4uIn0" \
  -H "Authorization: Bearer imma_live_xxxxxxxxxxxxxxxxxxxx"

Practical advice

• Treat a cursor value as opaque; do not construct or parse it yourself.
• Do not assume a fixed page size; combine other filters (status, date range, profile_id, platform) with pagination rather than paging through unfiltered results.
• A cursor from one filtered query is not valid for a different filter combination.

Errors

See Errors for the shared error shape.