Skip to main content
GET
Get credit balances

First time? Set up Authentication

Learn how to authenticate your API requests with your API key.
Reads the two credit balances of the workspace that owns the API key. The call does not search and does not spend credits. It does not require an active subscription. The request still counts in the per-key rate-limit windows. Query parameters are ignored. The workspace always comes from the API key.

Response

When success is true, data contains:
  • api.remaining — API credits still available for talent search and qualified search. This is the sum of unexpired API credit grants, the same number as the X-Api-Credits-Remaining header on routes that send it. Credits held by a running qualified search are not included until they are returned. This is not creditsRemaining from a qualified-search result, which is the budget left on that call.
  • contact.remaining is the contact-credit balance shown in the Kalent app: the credits granted at the last plan reset, plus credits added since, minus credits spent since. Enrichments still in progress are not deducted yet. It can differ from the amount Kalent checks before starting an enrichment or sending an SMS. When they differ, the enrichment response (402 insufficient_credits) or the paused sequence is what applies. The value can be 0 before the first plan reset, and it is not floored at 0.
This route does not send X-Api-Credits-Used or X-Api-Credits-Remaining.

Errors

A workspace with no balance history returns 0 for both fields. The route does not respond with 402 or 404.