Copy page

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:

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

Prices are on the pricing page. 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.

"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

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