Understanding Credit Usage for High-Volume API Requests

When running large API requests — searching for employees, enriching lead lists, or pulling records across companies — credits can add up faster than expected. This guide explains how usage is calculated and how to stay in control.

How credits add up

Some endpoints (like Person Search or Employee Listing) charge per result returned, not per call. For example:

• 1 API call returning 100 employees
• At 3 credits per result
• = 300 credits used in a single call

This is expected behavior, but it can catch you off guard if you're not accounting for your default page_size.

Best practices to prevent unexpected charges

1. Set page_size to control volume

By default, page_size is 100 — meaning up to 100 records could be returned per call. Set a smaller value to limit cost:

{
  "page_size": 25
}

Using page_size of 10, 25, or 50 is ideal for testing in smaller chunks.

2. Avoid duplicate or repeated calls

Each API call is charged separately, even with the same parameters. Examples to watch out for:

• Running the same role or person search query more than once
• Repeating a company profile lookup during troubleshooting

Each call deducts credits based on results returned.

3. Review your usage logs

If you notice a larger credit drop than expected, contact us at [email protected] — we can review your recent usage logs and help clarify what happened.

Common credit usage triggers

If you're working on backend automation or scaling API calls, test with smaller datasets first to keep per-call credit usage predictable.