# Pagination When a response is paginated, the response headers will include a link header. If the endpoint does not support pagination, or if all results fit on a single page, the link header will be omitted. The link header contains URLs that you can use to fetch additional pages of results. For example, the previous and next page of results. If the response is paginated, the link header will look something like this: ``` link: ; rel="prev", ; rel="next" ``` The link header provides the URL for the previous and next page of results: The URL for the previous page is followed by rel="prev". The URL for the next page is followed by rel="next". In some cases, only a subset of these links are available. For example, the link to the previous page won't be included if you are on the first page of results. You can use the URLs from the link header to request another page of results. --- # Agent Instructions: 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: ``` GET https://developerdocs.instructure.com/services/parchment-digital-badges/pagination.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.