Pagination

11min

Pagination information for the /v1/professional_network/company/search/es_dsl  endpoint.
Shortcuts
﻿Pagination using cURL requests﻿
Examples of pagination usage with cURL requests. 
Overview
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 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: 68112 
 x-total-pages: 217 
 x-total-results: 216573 
 x-next-page-after: 68112 
 x-total-pages: 217 
 x-total-results: 216573 
﻿
x-next-page-afterdisplays the last ID on the page.
x-total-pages lists the total number of pages with ID results.
x-total-resultsshows the total number of IDs returned by your search. 
Using pagination in cURL requests
This tutorial requires prior knowledge of how to compile and execute POST requests in Company API.
﻿Company POST ES DSL requests﻿
Elasticsearch DSL endpoint
Use parameterx-next-page-after to retrieve a second page of IDs.
Navigate to the Headers section and click it:
﻿
2. Find the following information:
x-next-page-after 
x-total-pages
x-total-results 
﻿
﻿
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-resultsshows 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:
JSON
[
1000,
1001,
3000,
4004
]
[
1000,
1001,
3000,
4004
]
﻿
Pagination using sorting
﻿Sorting in Elasticsearch DSL endpoint﻿
Pagination, when sorting by ID, works the same way as pagination without sorting. 
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/v1/professional_network/company/search/es_dsl?after=636106' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {JWT}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
        "bool": {
            "must": [
                {
                    "query_string": {
                        "query": "(3D printing) OR (3D printing service) OR (Lead generation)",
                        "default_field": "description",
                        "default_operator": "and"
                    }
                }
            ]
        }
    },
  "sort": [
        "id"
    ]
}'
curl -X 'POST' \
'https://api.coresignal.com/cdapi/v1/professional_network/company/search/es_dsl?after=636106' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {JWT}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
        "bool": {
            "must": [
                {
                    "query_string": {
                        "query": "(3D printing) OR (3D printing service) OR (Lead generation)",
                        "default_field": "description",
                        "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.
﻿
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/v1/professional_network/company/search/es_dsl?'?after=28.221064,33539870 \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {JWT}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
        "bool": {
            "must": [
                {
                    "query_string": {
                        "query": "(3D printing) OR (3D printing service) OR (Lead generation)",
                        "default_field": "description",
                        "default_operator": "and"
                    }
                }
            ]
        }
    },
  "sort": [
        "_score"
    ]
}'
curl -X 'POST' \
'https://api.coresignal.com/cdapi/v1/professional_network/company/search/es_dsl?'?after=28.221064,33539870 \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {JWT}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
        "bool": {
            "must": [
                {
                    "query_string": {
                        "query": "(3D printing) OR (3D printing service) OR (Lead generation)",
                        "default_field": "description",
                        "default_operator": "and"
                    }
                }
            ]
        }
    },
  "sort": [
        "_score"
    ]
}'
﻿
Send the request, and you will see the next page in the (Response) Body.  
﻿

Updated 16 Sep 2024

Did this page help you?

Elasticsearch DSL

Postman Tutorial

Pagination

Shortcuts

Pagination using cURL requests

Overview

Why is pagination needed?

Where can I see the page count?

Response header infomation

Using pagination in cURL requests

Company POST ES DSL requests

Elasticsearch DSL endpoint

Pagination using sorting

Sorting in Elasticsearch DSL endpoint

Pagination

Shortcuts

﻿Pagination using cURL requests﻿

Overview

Why is pagination needed?

Where can I see the page count?

Response header infomation

Using pagination in cURL requests

﻿Company POST ES DSL requests﻿

Elasticsearch DSL endpoint

Pagination using sorting

﻿Sorting in Elasticsearch DSL endpoint﻿

Pagination using cURL requests

Company POST ES DSL requests

Sorting in Elasticsearch DSL endpoint