Account
Account details, usage, request logs, and rate limits
Get Account
Returns your account, your plan, and your credit usage in the current usage window.
requests.domains,requests.verifications, andrequests.counthold your search, verification, and email count allowances (available) and what you've used (used). The remaining balance isavailableminusused.issuedandexpiredbound the current usage window.expired_subscriptionis when the subscription period ends.pricing.available_searchesandpricing.available_verificationsinclude your unused credit-pack credits, whichaddon_creditslists separately.secret_tokenis your API secret. Don't log or share this response.
This endpoint is rate-limited per plan under the route name me; see Rate limits. It also accepts an OAuth 2.0 access token with the read scope. See Check usage for the other ways to track credits.
Get Account › Responses
Your account details.
Your account, plan, and credit usage in the current usage window.
Retrieve API Usage
Returns your daily credit usage over a range of days, one row per user and day, with totals for the range.
durationsets the range: from that many days ago through today. Rows exist only for days with charged credits.scope=teamreturns the rows of every member of your workspace, andscope=memberthe rows of one member. Both need the workspace owner or admin role.- A workspace owner's rows also include the credits that members used on most endpoints, because those count against the owner's pool. With
scope=team, those credits appear in both the member's rows and the owner's.
The endpoint also reads start, end, and period, but they have no effect on the result: start and end in YYYY-MM-DD form are ignored, an RFC 3339 value fails with 500, and period is validated (daily, weekly, or monthly) but not used. Use duration.
Call this endpoint with an API key and secret. OAuth access tokens aren't accepted and get 401. See Check usage.
query Parameters
scopeWhose usage to return: user (yours), team (every member of your workspace), or member (the member in member_id). team and member need the workspace owner or admin role and otherwise fail with 403.
member_idWith scope=member, the user ID of a member of your workspace. When it's missing, or the user isn't in your workspace, the response has your own usage.
durationNumber of days to look back from today. The range includes today, so 7 covers eight days. Other values fail with 422.
Retrieve API Usage › Responses
Daily usage rows and their totals.
One row per user and day with charged credits, oldest first. Days without charged credits have no row. The source_* counters split the day's credits, of every type, by where the requests came from. null when the range has no rows.
Sums over the rows in data. There's no email_count total.
Retrieve API Logs
Returns your billable lookups, newest first, with what each one cost. Only requests to endpoints that cost credits, and that returned 200 with a result, are logged. Repeats of a lookup already charged in the current usage window appear with cost 0. Failed requests, lookups without a result, and free endpoints aren't logged.
In a workspace, the response includes the rows of every member; member_id narrows it to one member. data is null when no row matches.
Call this endpoint with an API key and secret. OAuth access tokens aren't accepted and get 401.
query Parameters
pagePage number, starting at 1.
limitRows per page, up to 100. Larger values fail with 422.
directionSort order by row ID. desc returns the newest rows first.
member_idUser ID of a member of your workspace, to return only their rows. An ID outside your workspace is ignored.
typeCredit type to match: search, verifier, email_count, or sources. Rows show the lookup's name in type instead.
sourceWhere the requests came from: source_api, source_website, source_extension, source_sheets, source_bulk, source_mcp, or source_snowflake. Rows show a display name in source instead.
costpaid returns rows with a cost above 0, free rows with a cost of 0.
status_codeHTTP status to match. Every logged row has 200.
http_methodHTTP method to match, for example GET.
ip_addressCaller IP address to match.
startEarliest created_at to include, in RFC 3339 format such as 2026-09-01T00:00:00Z. A value in another format, such as 2026-09-01, is ignored.
endLatest created_at to include, in RFC 3339 format. A value in another format is ignored.
qText to look for in hash, route_name, ip_address, endpoint, and request_id.
Retrieve API Logs › Responses
A page of log rows.
Log rows. null when no row matches.
Pagination details.
Retrieve a Single API Log
Returns one row of GET /logs by its id. In a workspace, you can read the rows of every member.
The API also matches logId against the row's request_id, but rows logged by the current API don't record one, so use id.
Call this endpoint with an API key and secret. OAuth access tokens aren't accepted and get 401.
path Parameters
logIdThe row's id.
Retrieve a Single API Log › Responses
The log row.
One billable lookup. Only requests to endpoints that cost credits, and that returned 200 with a result, are logged, including repeats charged 0.
Retrieve rate limits
Returns, for every rate-limited route, the limits that apply to your account and the requests counted against them in the current minute and day.
- The limits come from your plan, raised by any credit pack that still has credits.
0means unlimited. - In a workspace, members get the owner's limits, and the usage counts cover the whole workspace. Every API key, OAuth app, and member of an account or workspace shares these counters.
- Daily counts reset at 00:00 UTC.
pricing.rate_limits in GET /me shows your own plan's limits; this endpoint shows the limits actually enforced on your requests. It isn't rate-limited itself. It also accepts an OAuth 2.0 access token with the read scope. See Rate limits.
Retrieve rate limits › Responses
Limits and usage for each route.
One entry per route name. The response always has these 21 keys: domain-search, email-finder, email-verifier, email-count, email-sources, email-format, author-finder, enrich, linkedin, phone, phone-validator, similar, technology, domain-suggestions, me, searches, location, enrich-email, enrich-company, enrich-combined, and reveal.
Most keys match the endpoint path. The others:
phonecovers/phone-finder.enrich-email,enrich-company, andenrich-combinedcover/people/find,/companies/find, and/combined/find.searchescovers searches made in the Tomba dashboard.revealis listed but not enforced, so its usage is always0./reveal/searchhas a fixed limit instead.