Skip to main content
Huntr returns one page per request. The API does not auto-fetch additional pages for you.

​
The loop

Every paginated endpoint uses the same client loop:
  1. Call the endpoint with your filters or URL.
  2. Read pagination.has_more and pagination.token from the response.
  3. If pagination.has_more is false or pagination.token is null, you are done.
  4. Otherwise call again with the same body (query, company_url, URL, etc.) and pagination: { "token": "..." }.
Tokens are opaque. Do not decode, modify, or reuse them with a different query or URL. Endpoints: POST /company-search, POST /person-search Request:
  • size — requested rows for configurable-size endpoints. Company search min 1, default 10, max 100. Person search min 1, default 100, max 200.
  • token — omit on the first page.
Response:
Keep the query identical between pages. For person search, also keep has_email and has_phone identical when you use those flags.

​
LinkedIn pages

Endpoints:
  • POST /company-linkedin-posts — 10 posts per page
  • POST /linkedin-post-reactions — 10 reactions per page
  • POST /linkedin-post-comments — 100 comments per page
Request: only pagination.token is supported (no size).
Response:
Keep the same linkedin_url or post_url between pages. Billing is per page, not per row.

​
X pages

Endpoints:
  • POST /x-post-search
  • POST /x-thread
Request: only pagination.token is supported. Huntr does not accept pagination.size because page size is Huntr-controlled for these endpoints. Response: pagination.size is the number of X posts returned in result.tweets for that response page.

​
Response size

In every paginated response, pagination.size is the number of items returned in that response page. It is not the requested size and it is not the total available count. When a real total is available, Huntr returns it separately as top-level total.

​
Count endpoints

Count endpoints such as /company-search-count and /person-search-count are not paginated. Do not send pagination, limit, page_token, cursor, start, offset, or page; the response returns total only.

​
Usage history (exception)

GET /usage paginates your request log with limit and offset query parameters. That endpoint is for account history, not GTM list building.

​
Next step