Descovo search endpoints — people search and company search — use cursor-based pagination. Rather than page numbers, the API returns an opaqueDocumentation Index
Fetch the complete documentation index at: https://docs.descovo.com/llms.txt
Use this file to discover all available pages before exploring further.
nextCursor value with each response. You pass that cursor into your next request to fetch the following page of results. When nextCursor is null, you have reached the end of the result set.
Pagination parameters
The number of results to return per page. Minimum is 1, maximum is 1000. Defaults to 25 if omitted.
The cursor value returned as
nextCursor in the previous response. Pass null or omit this field to fetch the first page.Pagination in responses
An opaque string you pass as
cursor in your next request. Returns null when there are no more results to fetch.Example: walking through company search results
First page — omitcursor or set it to null:
nextCursor value as cursor:
nextCursor is null.
When to stop paginating
Stop fetching pages when:output.nextCursorisnull— you have retrieved all matching results.- You have collected as many results as your workflow requires.
Tips for reliable pagination
- The cursor encodes the position in the result set. It is opaque — do not try to parse or modify it.
pageSizedoes not need to match between requests, but keeping it consistent is easiest.- Both people search and company search use the same cursor-based model with identical parameter names.
- For large result sets (thousands of records), consider using audiences instead of paginating through raw search results. Audiences let you save and process results without holding them all in memory.