Billing

Returns the remaining credits balance for your organization.

Use this endpoint to check how many credits you have available before running large batches or to monitor usage programmatically.

What Are Credits?

Credits are the single currency for every metered Saber API operation. Current costs:

• Company & contact signals (POST /v1/companies/signals[/sync|/batch], POST /v1/contacts/signals[/sync], and their entity-first aliases POST /v1/companies/enrich/custom[/batch] and POST /v1/contacts/enrich/custom) — 2 credits per signal (batch: per signal created); repeat calls served from cache are free
• Prebuilt signals (POST /v1/signals/[sync/]{funding|mna|tech|open-jobs|firmographics}) — 2 credits per result delivered to your organization
• Prebuilt enrichment (POST /v1/companies/enrich/{type}) — priced per type: funding 0.3, open-jobs 0.5, firmographics 0.6, mna 0.75, tech-stack 0.75 credits per result delivered; cached results free, including results already paid for via the legacy signals surface
• Signal subscription runs — the schedule/trigger is free; every signal a run freshly generates charges 2 credits (cached results free)
• Contact research (POST /v1/contacts/research) — 2 credits per request
• Email finder (POST /v1/contacts/find-email) — 0.1 credits per successfully processed request; a found email and a verified not-found both charge (the verification work ran either way), errors are free
• Market signals — subscriptions are free to configure; each signal created (stored) by a polling run charges 8 credits, independent of webhook delivery
• Company list creation with a technologies filter — 1 credit per matched company, charged on the creation-time estimate; preview the same estimate for free via POST /v1/companies/lists/count-preview
• Everything else — reads, listing, templates, summaries, subscription configuration and lifecycle — is free

Failed signal runs, failed research jobs, and rejected email-finder requests are not charged. Market-signal charges apply once a signal is stored, independent of webhook delivery. Credits reset at the start of each billing period.

When to Use This Endpoint

• Before large batches: Check that you have enough credits before submitting a bulk request
• Monitoring dashboards: Poll periodically to display current usage
• Conditional logic: Skip signal generation if credits are exhausted

Example

curl https://api.saber.app/v1/credits \  -H "Authorization: Bearer YOUR_API_KEY"

Response Body