Pagination and sorting

Ticket search and a ticket's messages come back a page at a time. Ticket search comes newest activity first; a ticket's messages come oldest first.

• limit sets the page size, from 1 to 100. When you leave it out it is 25 for ticket search and 50 for a ticket's messages.
• Pass next_cursor back as cursor to get the next page. When next_cursor is null (has_more is false) you have every row.
• A cursor is signed. It works only for the list and the workspace it came from; anything else is refused with cursor_invalid.
• A cursor works only with the order it came from. One from the other order is refused with cursor_invalid.

curl -sS --fail-with-body "https://api.current.day/v1/tickets?limit=100" \
  -H "Authorization: Bearer $CURRENT_API_KEY"

# then, while next_cursor is not null:
curl -sS --fail-with-body "https://api.current.day/v1/tickets?limit=100&cursor=<next_cursor>" \
  -H "Authorization: Bearer $CURRENT_API_KEY"

In the default order (sort=activity, newest activity first), a ticket that gets new activity while you page moves to the top and is not seen again in that walk. A thread's new messages come at the end, on the last page.

To keep a copy in step, page with sort=created and updated_since: that order does not move while you page, so every ticket changed since your last run comes back exactly once. Start each run at the time the last one started.

curl -sS --fail-with-body "https://api.current.day/v1/tickets?sort=created&updated_since=2026-10-30T00:00:00Z&limit=100" \
  -H "Authorization: Bearer $CURRENT_API_KEY"
# then pass next_cursor back as cursor, with the same sort and updated_since, until it is null