Paging, dates and ids

How lists come back, and the formats used everywhere.

Paging

Lists that can be long take offset and limit and answer with:

{
  "data": [],
  "has_more": true,
  "next_offset": 50
}

Pass next_offset as the next request's offset until has_more is false:

def all_items(api, project_id):
    offset = 0
    while True:
        page = api.get(f"/projects/{project_id}/items", params={"offset": offset, "limit": 100}).json()
        yield from page["data"]
        if not page["has_more"]:
            return
        offset = page["next_offset"]
ListDefaultMost per page
Most lists50100
Content (/v1/content)30100
Automation runs25, newest first, with limit only200
PeopleAll of them200
Job roles, playbooks, KPIsAll of them

Formats

  • Ids are UUID strings.
  • Dates are YYYY-MM-DD, like 2026-12-05.
  • Times are ISO 8601 with a UTC offset, like 2026-11-21T15:04:05+00:00.
  • Links: anything that can be opened in the app has a url field.
  • New fields can appear in answers at any time. Ignore fields you don't know. See the changelog.