> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v9/api-flows/api-consumption/consume/pagination.md).

# Pagination

Pagination refers to managing the traffic of records coming from a source. It divides the records into a discrete number of pages so that they are comprehensible for a user. Pagination is not supported by all APIs. For those that do support it, Astera offers four types of paginations.

## **Offset**

This type of pagination requires two parameters: A *Limit* and an *Offset* value to be specified by the user. A *Limit* specifies the number of records that you want to specify on one page, and an *Offset* simply tells the number of records to be skipped before selecting records.

* *Initial Offset*: The record from which you want to start your pagination.
* *Number of Pages:* The number of pages that you want to be processed.
* *Limit*: Number of records on one page.
* *Offset Parameter*: Here, you can specify the offset parameter of the API that you are working with, as specified on the *Parameters* screen.
* *Limit Parameter*: Here, you can specify the limit parameter of the API that you are working with, as specified on the *Parameters* screen.

![](/files/vBjYmVjM8G8W5tLJu2GL)

## **Cursor**

This type of pagination generates a token for the next page of records. You can set a limit to the number of pages you want to process.

* *Cursor Field*: Here, you can specify the field you want to attach your cursor with.
* *Number of Pages*: Here, you can specify the number of pages you want to see in your output, or you can simply check the *Read till End* option if you want to process all records without any limit.
* *Cursor Parameter*: Here, you can specify the cursor parameter of the API that you are working with, as specified on the *Parameters* screen.

![](/files/nwNX58rgpKXrFZlNOzdL)

## **Next URL**

This type is the same as *Cursor* pagination, except that it generates a URL instead of a token for every subsequent page.

* *Next URL Field*: Here, you can specify the field you want to attach your URL with.
* *Number of Pages*: Here, you can specify the number of pages you want to see in your output, or you can simply check the *Read Till End* option if you want to process all records without any limit.

![](/files/edoongxzhawYL8RvL5dq)

## **Page Number**

In this type of pagination, you can specify the number of pages you would like to fetch in one go. It requires two parameters:

* *Start Page Number*: The page number from where you want to start fetching your output, or the lower limit.
* *End Page Number*: The page number where you want to end.
* *Page Number Parameter*: Here, you can specify the page number parameter of the API that you are working with, as specified on the *Parameters* screen.

![](/files/naR0M0BZJe9DbF4Hwojz)

This concludes our discussion of pagination for APIs in Astera.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.astera.com/astera-data-stack-v9/api-flows/api-consumption/consume/pagination.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.