Skip to content
Stackly
Log inStart free

Pagination changes in API v1

by Tomas Eklund

Every list endpoint in API v1 now uses cursor pagination. Each response carries a next_cursor field, and you pass it back as the cursor parameter to read the next page. The limit parameter defaults to 50 and the maximum is 200.

We kept the offset parameter so existing integrations do not break on the day of the change. It keeps working until March 1, 2027, and after that date requests that use offset receive an invalid_field error.

Cursors stay valid while tasks are added or removed, which offsets never did. If you page through a busy project with offset, you can skip or repeat tasks; with a cursor you cannot.

In short

Reader comments

No comments yet.

Related