Specification Changes to the Number of Items (cnt) and Page Number (pageID) of List Endpoints
Published: 2026-11-17
In the January 2027 general release, the handling of cnt (number of items per page), pageID (page number), and pageInfo in endpoints that return lists will be aligned with the content list endpoint (Topics::list). Please check how you call your endpoints and take the necessary actions before the release.
This also applies when you call endpoints that return lists with api_internal or api_method in custom functions.
When you specify cnt=0
Changes
The following endpoints will return all items when cnt=0 is specified. In this case, pageInfo will contain only totalCnt, and pageID is ignored even if specified. The same applies when 0 is specified for cnt in the endpoint settings. Currently, they return 20 items per page even when cnt=0 is specified.
MemberCustomSearch::listMemberProvisional::listMagazineInfo::listMagazineSubscriber::listLoginHistory::listLoginFailed::listSite::listAiAgent::get_sessionsSpiderHistory::listECPoint::historyMagazine::list(when0is specified forcntin the endpoint settings. Whencnt=0is specified as a query parameter, it already returns all items.)
TopicsCategory::list continues to return all items when cnt=0 is specified, but pageInfo will contain only totalCnt.
Required actions
- To keep retrieving 20 items per page as you do now, specify
20forcnt. - If you page through results with
pageID, or if you use items ofpageInfoother thantotalCnt, also specify 1 or more forcnt.
When you specify a pageID beyond the last page
Changes
Endpoints that return lists will return a 404 error when a pageID beyond the last page is specified. Currently, many endpoints return the last page or an empty list.
- When there are 0 items, a
pageIDof 2 or more returns a 404 error. - Endpoints that return all items on one page when
cntis omitted (such asTopicsCategory::list) also return a 404 error for apageIDof 2 or more.
Required actions
Refer to totalPageCnt in pageInfo and do not specify a pageID beyond the last page.
When you specify the number of items with per_page, perPage, or setPerPage
Changes
Endpoints that return lists will ignore the per_page, perPage, and setPerPage query parameters. Currently, some endpoints accept these parameters to specify the number of items per page.
Required actions
Change your requests to specify the number of items with the cnt query parameter.
When you handle numbers in pageInfo as strings
Changes
Numbers in pageInfo, such as perPage, will always be returned as integers. Currently, some endpoints return perPage and other numbers as strings when cnt is specified.
Required actions
If you compare numbers in pageInfo as strings, change your code to handle them as integers.
Added query parameters
The following query parameters will also be added. The number of items returned when cnt is omitted does not change.
| Endpoint | Added query parameters |
|---|---|
MemberGroup::list, Batch::list, CustomProcessing::list | cnt (number of items per page; 20 if omitted, all items with 0), pageID (page number) |
Rollout Timeline
These changes are planned to be reflected in the January 2027 general release.
Contact
If you have any further questions regarding this matter, please feel free to contact Kuroco Support.
Related documents
Support
If you have any other questions, please contact us or check out Our Slack Community.