Skip to main content
Credits are your workspace’s currency for data operations. Every search result, saved row, and enrichment draws from a single workspace-level balance — the same one your team spends in the app, so API usage and in-app usage debit the same pool.

​
Check your balance

Check it before large operations — a save-to-list of thousands of rows debits per row saved.

​
What debits credits

POST /business/prospects/search/save-to-list does not reuse a prior POST /prospects/search — passing the same filters runs the search again, so previewing first and then saving pays for the search twice. Preview with small limit values to tune filters, then call save-to-list once. Saving a hand-picked subset of results is not supported; narrow filters instead.
This design exists because saving is a server-side pipeline: the search, the save, and the follow-on enrichment run as one job, which is what lets a single call populate a fully enriched list. The build-a-list guide shows the cheap preview-then-save workflow end to end.

​
What never debits credits

Reads are free: listing lists, reading rows, checking campaign status, polling and downloading exports. You can poll as often as your rate limits allow — rate limits are a separate mechanism and always apply, whether or not a request costs credits.

​
Insufficient balance

When your balance cannot cover an operation, the request fails up front with INSUFFICIENT_CREDITS — before any work runs, so nothing is billed. Top up or reduce the request size, then retry.

​
Plans and pricing

Credit allowances and pricing vary by plan, so this page deliberately quotes no numbers. Your plan’s details and top-up options live on the Billing page in the app.