It would be great in the Content API, to be able to get the total amount of items in the return of the getAll method.
That would allow us to be able to display a very common pagination pattern with numbered pages.
At the moment, we do not know if there is more content to query when limiting a query to X number of items.
This is available on the Content API via a
fetchTotalCountparam. Add&fetchTotalCount=trueto the end of your query and you will see atotalCountkey that has the number of total results for the model. That number can be used for pagination or other use-cases where you need to know the total results.For the Content API, we'll be adding this to the docs as well as the API Explorer to surface it better.
We will also be working to add this to the
getAlloptions for use via SDK. In the meantime, you can get this using the direct fetch method instead ofgetAll.Checking in on this feature in 2026. Seems like this has been requested for Years. Any chance this is on the docket?
Hi, its 2025 November and still this basic feature is not yet implemented, what kind of stupidity is this? If someone uses your api its basic that you should provide the totalcount of the records to paginate.
Hi, it is 2025 and still not implemented. Such a basic functionality supported by other CMSes. Bummer.
This has been requested for a long time on the forums, and is a basic feature of pagination. Low effort win here.
This is a big issue for us, which seems on the surface as a relatively minor feature to add!
Lower effort, big win?
Builder dev team, any chances to implement that anytime soon?
Really important feature to be able to build full pagination components when having lot of content on a data model.