Employee Data
...
Endpoints
Search Filters
Pagination
9min
learn how to use pagination in base employee api https //api coresignal com/cdapi/v2/employee base/search/filter endpoint shortcuts pagination docid 3whudqim9x7oefpe4ue26 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 contain information such as the total result count , page number , and the last id on the page example x next page after "2024 05 20 15 35 28",40513386 x total pages 2 x total results 1053 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 base employee api search filter 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 pagination example curl x 'post' \\ 'https //api coresignal com/cdapi/v2/employee base/search/filter?after="2024 05 20 15 35 28",40513386' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "updated at gte" "2022 05 26 12 41 10", "certification title" "data processing", "experience title" "python developer" }' 4\ execute the request, and you will see the next page in the body section \[ 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 items per page curl x 'post' \\ 'https //api coresignal com/cdapi/v2/employee base/search/filter?items per page=150' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "updated at gte" "2022 05 26 12 41 10", "certification title" "data processing", "experience title" "python developer" }'