TombaTomba
Start free
  • Documentation
  • API reference
  • SDKs & CLI
  • AI & MCP
  • Integrations
  • Enterprise
  • Migration guides

Find, verify and enrich B2B contacts from public sources, in the app, your spreadsheet or through the API.

GDPR & CCPA

// docs

  • API changelog
  • Support options
  • Security

// platform

  • Dashboard
  • Pricing
  • API status

// resources

  • Help center
  • Product updates
  • TombaBot crawler

// company

  • Website
  • Contact us
  • Edit or remove your data

© 2021–2026 Tomba.io

  • Terms of service
  • Privacy policy
  • Cookie policy
  • Security policy
  • GDPR
  • CCPA
Get started
Platform
    Credits and usageRate limitsErrorsWebhooksVersioningAll limits
API guides
Response reference
Policies
Resources
Platform

Credits and usage

Most Tomba endpoints consume credits from a monthly allowance. This page is the reference for what each request costs, when it's free, and how to check what you have left. Throttling is separate; see Rate limits.

Quotas

Your account has four credit balances:

BalanceUsed by
Search creditsFinders, enrichment, phone lookups, company search, similar domains
Verification creditsEmail verifier
Email count creditsEmail count, email format, location
Sources creditsEmail sources

New accounts start on the Free plan, with 25 search credits per usage window. Paid plans include equal search and verification allowances:

PlanSearch creditsVerification creditsAvailability
Basic2,5002,500Self-serve
Growth5,0005,000Self-serve
Pro20,00020,000Self-serve
Pro Plus50,00050,000Self-serve
Scale 100k100,000100,000On request
Scale 200k200,000200,000On request
Scale 350k350,000350,000On request
EnterpriseBy contractBy contractContact sales

Prices are on the pricing page; Tomba Enterprise covers the Enterprise plan. Email count and sources allowances depend on the plan and appear in GET /v1/me.

Usage window. Monthly subscriptions reset at each billing date. Free, yearly, and Enterprise plans reset every 30 days; yearly plans receive a monthly allowance, not an annual pool. Unused plan credits don't carry over.

Credit packs. Pay-as-you-go packs add credits on top of your plan. Pack credits last 365 days from purchase, carry over between windows, and are used only after your plan credits run out, oldest pack first.

Workspaces. Members of a workspace use the owner's credits. The owner can set a search or verification limit for each member; a member who reaches it gets 402 quota_exceeded.

Auto-upgrade. If you turn on auto-upgrade in the dashboard, your subscription moves to the next plan in the table above when 10% of your search credits remain. It never moves to Enterprise.

Credit costs

A request is charged only when it succeeds (HTTP 200) and returns a result that meets the "Charged when" condition. Errors, 429 responses, and 451 responses cost nothing.

EndpointCostCharged when
GET /domain-search1 search credit per 10 results requested with limit, rounded up (the default limit of 10 costs 1), plus 5 per returned address with phone dataAt least one email address is returned
GET /email-finder1 search credit, or 6 with phone dataAn address is returned with a verification status other than unknown
GET /author-finder1 search creditAn address is returned
GET /enrich1 search credit, or 6 with phone dataAn address is returned with a verification status other than unknown
GET /linkedin1 search credit, or 6 with phone data. With full=true: 1 per returned address plus 5 per phone numberAn address is returned
GET /email-verifier1 verification credit, plus 5 per phone number returned with enrich_mobile=trueThe status is not disposable or unknown
GET /phone-finder5 search credits, or 1 when the request includes domainA valid phone number is returned
GET /phone-validator1 search creditEvery successful response, including one with no data
POST /reveal/search1 search credit per requestAt least one company is returned
GET /similar1 search credit per 10 results requested with limit, rounded upResults are returned
GET /people/find1 search creditA person is returned
GET /companies/find1 search creditA company is returned
GET /combined/find2 search creditsA person is returned
GET /email-count1 email count creditEvery call
GET /email-format1 email count creditEvery successful call, including an empty result
GET /location1 email count creditEvery successful call, including an empty result
GET /email-sources1 sources creditSources are found
GET /technologyNot charged. Requires a positive search balance.—
GET /domain-suggestions, GET /domain-status, Logo APIFree—
Account and management endpoints (/me, /usage, /logs, /rate-limits, /keys, /leads, /flag)Free—
Bulk jobsPer row, depending on the bulk typeWhen you first download the results

"Phone data" means phone numbers returned because you set enrich_mobile=true.

If a request would cost more credits than you have left, it fails with 402 quota_exceeded before any work is done. When the email count or sources balance is exhausted, those endpoints return 429 rate_limit instead.

Duplicate requests

Sending the same request again within the same usage window costs nothing. The response still returns the data.

  • Same request means the same user, endpoint, and parameters. Changing any parameter, including page, limit, enrich_mobile, or webhook_url, makes a new request.
  • Some endpoints compare only their main input: the URL for author finder and LinkedIn finder, the email for person and combined enrichment, and the domain for company enrichment.
  • The rule is per user. Two members of a workspace sending the same request are each charged.
  • It doesn't apply to email count, email sources, or bulk jobs.
  • It resets with your usage window, so a repeat just after renewal is charged.

Refunds for incorrect data

When an email address returned by Tomba hard-bounces, report it with POST /v1/flag, flag_type email and reason hard_bounce. After Tomba reviews and confirms the report, one search credit is returned to your current usage window.

Other flag types and reasons correct the data but don't refund credits. A second report for an item that already has a pending report returns 409 duplicate_record. You can also review your reports under Flags in the dashboard.

Free plan limits

On the Free plan, outside a workspace:

  • Domain search returns at most 10 addresses. A limit above 10 fails with 400 params_invalid, and page is always 1.
  • Company search returns only the first page. A request for a later page returns the first page again, without the keyword, founded, revenue, type, technology, similar, SIC, and NAICS filters.
  • Similar domains and technology return only data Tomba already has, without a live lookup.

Check usage

WhereWhat it shows
Usage in the dashboardBalances and usage over time, for you or your whole workspace
GET /v1/mepricing.available_searches and pricing.available_verifications (plan plus pack credits); requests.domains and requests.verifications with available (the allowance) and used; the current window in issued and expired
GET /v1/usageDaily usage per balance
GET /v1/logsCharged requests with their cost; repeats appear with cost 0
Response headersX-Search-Limit / X-Search-Remaining, X-Verify-Limit / X-Verify-Remaining, X-Count-Limit / X-Count-Remaining, X-Sources-Limit / X-Sources-Remaining on charged endpoints. Values are from before the current request.

In requests.domains and requests.verifications, the remaining balance is available minus used.

Last modified on October 4, 2026
Going to productionRate limits
On this page
  • Quotas
  • Credit costs
  • Duplicate requests
  • Refunds for incorrect data
  • Free plan limits
  • Check usage