Were there recent changes to the totalPages parameter when querying the /sheets endpoint?

Up until last week, the totalPages and totalCount parameters functioned as expected when performing a simple GET call to /sheets. If there were 150 sheets, then it would show "totalPages": 2, "totalCount": 150. As of Friday of last week, it seems like it is showing "totalPages": 1, "totalCount": 100 any time there are more than 100 results. The page parameter can still be passed to read further pages, but totalPages and totalCount remain at 1 and 100 respectively. This is breaking our current integration, as we are iterating through pages of sheets to find specific ones by name. Was this a documented change? Is it a bug?

Find more posts tagged with

Sheets

Accepted answers

All comments

ericyyyffff

We have identified an issue in the Smartsheet API's pagination implementation for the /2.0/sheets endpoint. The API consistently returns incorrect values for pageNumber and totalPages fields in the response metadata, regardless of the actual pagination state.

Problem Details:

The pageNumber field always returns 1, even when requesting subsequent pages (e.g., page=2, page=3, etc.)
The totalPages field always returns 1, even when there are clearly more results available than the specified pageSize
The actual data pagination works correctly - different results are returned when changing the page parameter
The totalCount field appears to be accurate

Example: When making a request to https://api.smartsheet.com/2.0/sheets?pageSize=8&page=2, the response shows:

{

"pageNumber": 1,

"pageSize": 8,

"totalPages": 1,

"totalCount": 8,

"data": [...]

}

However, the expected response should show:

pageNumber: 2 (since we requested page 2)
totalPages: Should reflect the actual number of pages based on totalCount/pageSize

Impact: This bug prevents proper pagination logic implementation, as applications cannot reliably determine:

Which page of results they are currently viewing
How many total pages are available
Whether there are additional pages to fetch

Expected Behavior: The pageNumber should reflect the actual page being returned, and totalPages should accurately calculate the total number of pages based on the total count and page size.

ericyyyffff

I have the same issue , can anyone help on it?

Isaac A.

Thanks for bringing this up, @samturpin and @ericyyyffff.

After carefully reviewing our API documentation, specifically the Change Log, there isn’t any mention of a deprecation or a change to the /sheets endpoint related to the pagination fields you both described. Given that, this does appear to be unexpected behavior rather than an intentional change.

Because of this, the best next step is to contact our Support team so they can investigate further and confirm what’s happening.

I hope this helps!

Cheers,
Isaac.

ericyyyffff

It fails when I try to create a case

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.