Pagination

pagination information for the /v2/member/search/es dsl endpoint shortcuts pagination using curl requests https //docs coresignal com/api/employee api esdsl pagination#mzcfs examples of pagination usage with curl requests 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? response header infomation response headers will 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 11 07 22 53",542049888 x total pages 60 x total results 59431 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 how to compile post requests in employee api compiling employee es dsl post request https //docs coresignal com/api/employee api esdsl postman elasticsearch dsl endpoint use parameter x next page after to retrieve a second page of ids navigate to the headers section to the right of the (response) body 2\ click on the headers section you will need information from x next page after , x total pages , and x total results lines 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 pagination using sorting sorting in elasticsearch dsl endpoint https //docs coresignal com/api/employee api esdsl endpoint#8thve pagination, when sorting by id, works the same way as pagination without sorting all personal/company information mentioned within this context is entirely fictional and is solely intended for illustrative purposes pagination usage example (curl request in postman) add parameter ?after={last id} to the post request refer to the pagination example for the exact parameter placement pagination (sorted by id) curl x 'post' \\ 'https //api coresignal com/cdapi/v2/member/search/es dsl?after="2025 03 11 07 22 53",542049888' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "query" { "match" { "name" { "query" "john doe", "operator" "and" } } }, "sort" \[ "id" ] }' send the request, and you will see the next page in the (response) body pagination using id sorting works the same way as pagination without sorting 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 pagination example for the exact parameter placement pagination (sorted by score) curl x 'post' \\ 'https //api coresignal com/cdapi/v2/member/search/es dsl?after=11 8066225,"2023 07 11 15 47 51",445668330' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "query" { "match" { "name" { "query" "john doe", "operator" "and" } } }, "sort" \[ " score" ] }' send the request, and you will see the next page in the (response) body