Pagination
NocoDB API list requests return one page of results at a time. Record lists and the base list page in different ways.
Paging records
The v3 record and link endpoints return next and prev URLs beside records. Follow next until it is null.
A page after the last record is not an error. The response has an empty records list and a null next. Its prev points at the last page that has records, or at page 1 when the result set is empty. The base list above is different: there, an offset past the end returns an error.
Paging the base list
GET /api/v3/meta/workspaces/{workspaceId}/bases returns every base in the workspace. To get one page instead, send limit with the number of bases you want, and offset with the number to skip. NocoDB ignores offset when you send no limit.
Each response has a pageInfo object beside list. totalRows counts every base that you can see in the workspace. pageSize is the page size that NocoDB applied. It is smaller than your limit when the deployment caps it, so page with pageSize and not with the limit that you sent. A self-hosted deployment sets this cap with NC_DB_QUERY_LIMIT_MAX.
An offset at or above totalRows returns an error, not an empty page.
Related
Last updated on