Pagination

learn how to use pagination in clean employee api /v2/employee clean/search/es dsl endpoint overview why is pagination needed? profile ids are provided in batches of 1000 ids per page sometimes, a request might yield more ids than can be displayed on a single page in such situations, you'll need to use pagination to obtain all the requested ids from the post request where can i see the page count? respose header infomation response headers contain information such as the total result count , page number , and the last id on the page response header information you need to look for example x next page after "2025 03 15t00 00 00 000z",25828893 x total pages 2878 x total results 2877215 x next page after displays the last id on the page x total pages lists the total number of pages with id results x total results shows the total number of ids returned by your search using p agination in curl requests this tutorial requires prior knowledge of compiling and executing post requests in clean employee api elasticsearch dsl endpoint use parameter x next page after to retrieve a second page of ids navigate to the headers section and click it 2\ find the following x next page after , x total pages , and x total results information x next page after displays the last id on the page x total pages lists the total number of pages available for your search x total results shows the total number of ids available 3\ add parameter ?after={last id} to the post request to see the next results page 4\ execute the request, and you will see the next page in the body section \[ 1000, 1001, 3000, 4004 ] pagination using sorting elasticsearch dsl docid\ pkoqnjhsbflf7svuhv5au when sorting by id, pagination works the same way as pagination without sorting pagination usage example (curl request in postman) add parameter ?after={last id} to the post request refer to the example below for the exact parameter placement pagination (sorted by id) curl x 'post' \\ 'https //api coresignal com/cdapi/v2/employee clean/search/es dsl?after=1631164'\\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "query" { "bool" { "should" \[ { "query string" { "query" "python", "default field" "description", "default operator" "and" } }, { "query string" { "query" "python", "default field" "job title", "default operator" "and" } }, { "nested" { "path" "experience", "query" { "bool" { "should" \[ { "query string" { "query" "python", "default field" "experience description", "default operator" "and" } }, { "query string" { "query" "python", "default field" "experience title", "default operator" "and" } } ] } } } } ] } }, "sort" \[ "id" ] }' send the request, and you will see the next page in the (response) body pagination using score sorting has a different id format the format difference is seen by the x next page after parameter the number preceding the comma is for the score , and the one after the score is the last id on the page pagination usage example (curl request in postman) add parameter ?after={last id} to the post request to see the next results page refer to the example below for the exact parameter placement pagination (sorted by score) curl x 'post' \\ 'https //api coresignal com/cdapi/v2/employee clean/search/es dsl?after= 27 383614,639142776'\\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "query" { "bool" { "should" \[ { "query string" { "query" "python", "default field" "description", "default operator" "and" } }, { "query string" { "query" "python", "default field" "job title", "default operator" "and" } }, { "nested" { "path" "experience", "query" { "bool" { "should" \[ { "query string" { "query" "python", "default field" "experience description", "default operator" "and" } }, { "query string" { "query" "python", "default field" "experience title", "default operator" "and" } } ] } } } } ] } }, "sort" \[ " score" ] }' send the request, and you will see the next page in the (response) body