How Credits Are Calculated When Using the People Search Endpoint
How credit consumption works with the People Search endpoint, what affects usage, and how to keep costs under control.
When using the People Search endpoint, credits are charged per result returned — not per request. Understanding this helps you avoid unexpected charges and plan your usage more effectively.
How credit consumption works
Credits are charged at 3 credits per returned profile URL. This includes matches from your filtered query, such as job title, location, or employment status.
Example:
If your search returns 100 profiles, it costs:
3 credits × 100 results = 300 creditstext
This can add up quickly with high-volume requests or broader queries.
Factors that affect credit use
| Factor | Impact |
|---|---|
page_size not set | Defaults to 100 (can cost up to 300 credits per call) |
| Broad query filters | Returns more results, costing more |
| Additional enrichments | May incur extra credit charges |
How to reduce credit usage
- Set a lower
page_size— try 25 or 50 instead of the default 100 - Use tighter filters — narrow down your search to reduce results
- Test with smaller values before scaling up
{
"page_size": 25,
"region": "New York",
"current_role_title": "engineer"
}json