If you’re planning to run large API requests—like searching for employees, enriching lead lists, or pulling detailed records across companies—it’s easy to underestimate how quickly credits can be used.

This article walks through how usage is calculated in high-volume scenarios and what you can do to stay in control, especially while testing or iterating your setup.

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

This is expected behavior—but it can catch users off guard if you’re not aware of the default settings, such as page_size.

Here are a few ways to better manage your usage:

page_size

to Control Volume

By default, page_size is set to 100—meaning up to 100 records could be returned in one call.

To limit that, you can set a smaller value:

{

"page_size": 25

}

Choosing a smaller page_size (like 10, 25, or 50) is great for testing in smaller chunks and staying within your credit balance.

Even if your parameters are the same, each API call is charged separately.

Examples:

Each call deducts credits based on the number of results returned—even if the data looks similar.

If you notice a bigger credit drop than expected, our team is happy to help.

👉 Just send us a message or email [email protected], and we can review your recent usage logs to help clarify what happened—and guide you on optimizing future calls.

If you’re working on backend automation or scaling your API calls, try testing with smaller datasets first. It gives you better predictability and helps avoid using more credits than intended.

We’re here to help you make the most of your plan—with no surprises.

​