How page_size Affects Your Results and Credit Use

When using search endpoints like Person Search or Employee Listing, page_size controls how many results are returned per API call. Since credits are charged per result, page_size directly determines how much each call costs.

What is page_size?

page_size sets the maximum number of results returned in a single call. If you don't specify it, the default is 100.

A single Person Search call with no page_size set will attempt to return up to 100 profile URLs.

How page_size affects credit cost

Search endpoints charge 3 credits per returned result:

Credits used = 3 × number of results returned

If your search matches fewer profiles than your page_size, you're only charged for the actual results returned.

The default can be costly

Without setting page_size, the default of 100 means up to 300 credits in a single call. This is the most common cause of unexpected credit drops. For example, with 120 credits and no page_size set, a Person Search will fail — it tries to reserve 300 credits (3 × 100).

Best practices

• Always set page_size explicitly — don't rely on the default
• Start small when testing — use 10 or 25 while iterating on filters
• Scale up gradually — increase page_size once filters return relevant results
• Check your balance before large queries — ensure you have at least 3 × page_size credits available

Example requests

Conservative request for testing:

{
  "country": "US",
  "current_role_title": "software engineer",
  "page_size": 10
}

Costs a maximum of 30 credits.

Larger request once filters are validated:

{
  "country": "US",
  "current_role_title": "software engineer",
  "current_company_linkedin_profile_url": "https://www.linkedin.com/company/google",
  "page_size": 50
}

Costs a maximum of 150 credits.

Retrieving more results with pagination

If your search matches more profiles than your page_size, use the next_page token from the response to retrieve the next batch. This lets you pull large result sets in manageable chunks while keeping per-call cost predictable.

Questions about estimating query costs? Reach out at [email protected].