docs(api): add pagination instructions to REST API reference (cube-js#5300)

Author: hassankhan

docs/content/API-Reference/REST-API.mdx

@@ -40,18 +40,23 @@ curl -H "Authorization: EXAMPLE-API-TOKEN" https://example.com/cubejs-api/v1/sql
 ### <--{"id" : "Prerequisites"}--> Continue wait
 
 If the request takes too long to be processed, Cube.js Backend responds with
-`{ "error": "Continue wait" }` and 200 status code.
-This is how the long polling mechanism in Cube is implemented.
-Clients should continuously retry the same query in a loop until they get a successful result.
-Subsequent calls to the Cube endpoints are idempotent and don't lead to scheduling new database queries if not required by `refreshKey`.
-Also, receiving `Continue wait` doesn't mean the database query has been canceled, and it's actually still being processed by the Cube.
-Database queries that weren't started and are no longer waited by the client's long polling loop will be marked as orphaned and removed from the querying queue.
+`{ "error": "Continue wait" }` and 200 status code. This is how the long polling
+mechanism in Cube is implemented. Clients should continuously retry the same
+query in a loop until they get a successful result. Subsequent calls to the Cube
+endpoints are idempotent and don't lead to scheduling new database queries if
+not required by `refreshKey`. Also, receiving `Continue wait` doesn't mean the
+database query has been canceled, and it's actually still being processed by the
+Cube. Database queries that weren't started and are no longer waited by the
+client's long polling loop will be marked as orphaned and removed from the
+querying queue.
 
 Possible reasons of **Continue wait**:
 
 - The query requested is heavy, and it takes some time for the database to
-  process it. Clients should wait for its completion, continuously sending the same REST API request.
-  [continueWaitTimeout](config#queue-options) can be adjusted in order to change the time Cube waits before returning `Continue wait` message.
+  process it. Clients should wait for its completion, continuously sending the
+  same REST API request. [continueWaitTimeout](config#queue-options) can be
+  adjusted in order to change the time Cube waits before returning
+  `Continue wait` message.
 - There are many queries requested and Cube.js backend queues them to save
   database from overloading.
 
@@ -76,6 +81,30 @@ should be unique for each separate request. `spanId` should define user
 interaction span such us `Continue wait` retry cycle and it's value shouldn't
 change during one single interaction.
 
+### <--{"id" : "Prerequisites"}--> Pagination
+
+Cube supports paginated requests for the `/v1/load` endpoint by including
+[`limit` and `offset` parameters][ref-api-ref-query-format] in the query. For
+example, the following query will retrieve rows 101-200 from the `Orders` cube:
+
+```json
+{
+  "dimensions": ["Orders.status"],
+  "measures": ["Orders.count"],
+  "timeDimensions": [
+    {
+      "dimension": "Orders.createdAt",
+      "dateRange": "last year",
+      "granularity": "day"
+    }
+  ],
+  "limit": 100,
+  "offset": 100
+}
+```
+
+[ref-api-ref-query-format]: /query-format#query-properties
+
 ## API Reference
 
 ### <--{"id" : "API Reference"}--> /v1/load