> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/social-posts-data/employee-posts-api/search-filters/pagination.md).
# Search Filters Pagination: Employee Posts API
## Overview
General information about the pagination is listed in [Results Pagination](/api-introduction/requests/elasticsearch-dsl/results-pagination.md) topic.
Here you can find:
## Using pagination in cURL requests
{% hint style="info" %}
This tutorial requires prior knowledge of how to compile and execute POST requests in Employee Posts data API.
{% endhint %}
Use parameter `x-next-page-after` to retrieve a second page of IDs.
1. Navigate to the **Headers** section and click it:
2. Find the following information:\
– `x-next-page-after`\
– `x-total-pages`\
– `x-total-results`
3. Add parameter `?after={x-next-page-after}` to the POST request to see the next results page:
```json
curl -X 'POST' \
'https://api.coresignal.com/cdapi/v2/employee_post/search/filter?after="2025-07-14",7350452046057107456' \
-H 'accept: application/json' \
-H 'apikey: {API Key}' \
-H 'Content-Type: application/json' \
-d '{
"article_body": "newest invention",
"date_published_gte": "2025-07-01"
}'
```
4. Execute the request, and you will see the next page in the **Body** section:
```json
[
1000,
1001,
3000,
4004
]
```
## Limiting search results per page
Query parameter `?items_per_page={int}` allows you to specify the number of results retrieved per Search results page. The current limit is 1,000. Thus, this parameter lets you set a smaller limit value for the results page.
{% code title="Items per page" %}
```json
curl -X 'POST' \
'https://api.coresignal.com/cdapi/v2/employee_post/search/filter?items_per_page=250' \
-H 'accept: application/json' \
-H 'apikey: {API Key}' \
-H 'Content-Type: application/json' \
-d '{
"article_body": "newest invention",
"date_published_gte": "2025-07-01"
}'
```
{% endcode %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.coresignal.com/social-posts-data/employee-posts-api/search-filters/pagination.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.