Skip to content
Whats91

Page through Whats91 list endpoints with the page/limit and limit/offset conventions and read the pagination block correctly.

Pagination

Summary

Page through Whats91 list endpoints with the page/limit and limit/offset conventions and read the pagination block correctly.

Prerequisites

  • A Whats91 account

Whats91 list endpoints use one of two paging conventions. Reference and management endpoints page by page number; order endpoints page by offset. Both return a pagination object alongside the rows.

Page-Based Paging

Used by templates, webhooks, chatbots, contact books, blacklist entries, reports, conversations, and billing history.

ParameterTypeDefaultDescription
pageinteger1One-based page number. Values below 1 are clamped to 1.
limitinteger50Rows per page. Maximum 100; larger values are clamped.
Page through templates
curl "https://graph.whats91.com/api/v2/templates?page=2&limit=50" \
  -H "Authorization: Bearer w91_live_xxx"

Offset-Based Paging

Used by the order endpoints.

ParameterTypeDefaultDescription
limitinteger25Rows per request, 1 to 100.
offsetinteger0Number of rows to skip. Must be zero or positive.
Pagination block
{
  "pagination": {
    "limit": 25,
    "offset": 0,
    "count": 25,
    "total": 74,
    "has_more": true
  }
}

Paging Safely

  • Stop when has_more is false, or when the returned row count is smaller than the requested limit.
  • Records can be created while you page. For exports, filter by an explicit date range so the result set is stable.
  • Do not assume a fixed maximum page size across families; read the per-endpoint reference.
  • Report endpoints are counted against a separate platform rate limit, so a wide export should pace its requests.

Related Documentation