Offset pagination
Used by high-volume list endpoints — Contacts, Conversations, and a conversation’s Messages. The response includes a totalcount and absolute next / previous URLs:
The simplest way to page is to follow the
next URL until it’s null.
Cursor pagination
Used by Templates and other list endpoints. Cursor pagination is more stable when the underlying data changes between requests, so it does not include acount:
cursor value yourself — treat it as opaque and follow the next URL. When next is
null, you’ve reached the end.
Because cursor responses omit
count, you can’t know the total number of results up front — page until
next is null. Ordering is newest-first (by creation time).
