# CLI commands

This reference describes CLI version 1.2.3. Each command on this page calls the Tomba API with your credentials, so it uses credits and counts toward your limits exactly like the endpoint it calls: see [Credit costs](/usage-and-quotas#credit-costs) and [Rate limits](/rate-limits). Commands with their own pages: [`tomba bulk`](/cli/bulk), [`tomba chat`](/cli/chat), [`tomba serve`](/cli/http), [`tomba skill`](/cli/skill), [`tomba login` and `tomba logout`](/cli/authentication), and [`tomba version`, `tomba completion`, and `tomba update`](/cli/installation).

## Global flags

Every command accepts these flags.

| Flag         | Short | Type   | Default | Description                                                                                                         |
| ------------ | ----- | ------ | ------- | ------------------------------------------------------------------------------------------------------------------- |
| `--target`   | `-t`  | string | —       | The command's input: a domain, email address, URL, or text, depending on the command.                               |
| `--json`     | `-j`  | bool   | `false` | Print the response as JSON.                                                                                         |
| `--yaml`     | `-y`  | bool   | `false` | Print the response as YAML. Overrides `--json`.                                                                     |
| `--csv`      | —     | bool   | `false` | Print the response's `data` as CSV.                                                                                 |
| `--output`   | `-o`  | string | —       | Also write the response as JSON to this file. For `tomba bulk` and `tomba chat --file`, the path of the output CSV. |
| `--key`      | `-k`  | string | —       | API key. See [Pass credentials per command](/cli/authentication#pass-credentials-per-command).                      |
| `--secret`   | `-s`  | string | —       | API secret.                                                                                                         |
| `--no-color` | —     | bool   | `false` | Disable colored output. Setting the `NO_COLOR` environment variable to any value does the same.                     |
| `--port`     | `-p`  | int    | `3000`  | Port for [`tomba serve`](/cli/http). Other commands ignore it.                                                      |
| `--verbose`  | —     | bool   | `false` | Accepted, but has no effect.                                                                                        |
| `--help`     | `-h`  | —      | —       | Show help for any command.                                                                                          |

## Output and errors

By default, commands print a formatted summary. `--json` prints the response as JSON, syntax-colored only when the output is a terminal. `--yaml` output always contains terminal color codes, even with `--no-color`, so use `--json` when you redirect or parse the output. `--csv` suits flat responses; nested objects aren't flattened.

The list subcommands of `lead`, `leads-list`, `attribute`, `key`, and `flag` number the rows in their text output but don't show IDs. Run them with `--json` to get the `id` values that `get`, `update`, and `delete` take.

When a request fails, or when `search`, `finder`, `author`, `enrich`, `linkedin`, `verify`, `sources`, or `count` has no result, the CLI prints a short message instead of the response, even with `--json`. API errors appear as `error: <HTTP status>, status code: <code>`, such as `error: 429 Too Many Requests, status code: 429`; the response body isn't shown. See [Status codes](/error-handling#status-codes). The exit status is `0` in all of these cases; only usage errors, such as an unknown or missing flag, exit with `1`. In scripts, parse the output rather than the exit status, and add `--no-color`.

## Aliases

| Alias     | Runs                    |
| --------- | ----------------------- |
| `a`       | `tomba author`          |
| `ai`      | `tomba chat`            |
| `b`       | `tomba bulk`            |
| `c`       | `tomba count`           |
| `e`       | `tomba enrich`          |
| `l`       | `tomba linkedin`        |
| `pf`      | `tomba phone-finder`    |
| `pv`      | `tomba phone-validator` |
| `r`       | `tomba reveal`          |
| `s`       | `tomba finder`          |
| `sim`     | `tomba similar`         |
| `sk`      | `tomba skill`           |
| `t`       | `tomba status`          |
| `tech`    | `tomba technology`      |
| `upgrade` | `tomba update`          |
| `w`       | `tomba whoami`          |

The help for `tomba search` and `tomba sources` lists the alias `s`, and the help for `tomba verify` lists `t`, but those aliases run `tomba finder` and `tomba status`.

## `tomba search`

Find the email addresses Tomba has for a domain. Calls [`GET /v1/domain-search`](/api/finder#domain-search).

```text
tomba search --target <domain> [--limit 10|20|50] [--page <n>]
```

| Flag           | Short | Type   | Default | Description                                                                                                                          |
| -------------- | ----- | ------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| `--target`     | `-t`  | string | —       | Domain to search. Required.                                                                                                          |
| `--limit`      | —     | int    | `10`    | Addresses per page: `10`, `20`, or `50`. The CLI rejects other values. The value affects the [cost](/usage-and-quotas#credit-costs). |
| `--page`       | —     | int    | `1`     | Page of results.                                                                                                                     |
| `--department` | —     | string | —       | Has no effect: the CLI doesn't send it to the API.                                                                                   |

```bash
tomba search --target stripe.com
tomba search --target stripe.com --limit 50 --page 2
tomba search --target stripe.com --json --output stripe.json
```

The text output shows the organization, then a table of addresses with name, position, department, and confidence score. The Free plan restricts `--limit` and `--page`; see [Free plan limits](/usage-and-quotas#free-plan-limits).

## `tomba finder`

Find a person's email address from their name and company domain. Calls [`GET /v1/email-finder`](/api/finder#email-finder).

```text
tomba finder --target <domain> --first <first name> --last <last name> [--enrich-mobile]
tomba finder --target <domain> --full "<full name>" [--enrich-mobile]
```

| Flag              | Short | Type   | Default | Description                                                                                           |
| ----------------- | ----- | ------ | ------- | ----------------------------------------------------------------------------------------------------- |
| `--target`        | `-t`  | string | —       | Company domain. Required.                                                                             |
| `--first`         | `-f`  | string | —       | First name. Use with `--last`.                                                                        |
| `--last`          | `-l`  | string | —       | Last name. Use with `--first`.                                                                        |
| `--full`          | —     | string | —       | Full name, instead of `--first` and `--last`. Ignored when both are set.                              |
| `--enrich-mobile` | —     | bool   | `false` | Also return the person's phone number. Phone data changes the [cost](/usage-and-quotas#credit-costs). |

```bash
tomba finder --target stripe.com --first Jane --last Doe
tomba finder --target stripe.com --full "Jane Doe" --enrich-mobile
```

## `tomba author`

Find the email address of an article's author. Calls [`GET /v1/author-finder`](/api/finder#author-finder).

```text
tomba author --target <article URL>
```

| Flag       | Short | Type   | Default | Description                   |
| ---------- | ----- | ------ | ------- | ----------------------------- |
| `--target` | `-t`  | string | —       | URL of the article. Required. |

```bash
tomba author --target "https://stripe.com/blog/example-article"
```

## `tomba enrich`

Look up the person behind an email address: name, position, company, social profiles, and sources. Calls [`GET /v1/enrich`](/api/finder#email-enrichment). For separate person and company profiles, use [`tomba enrichment`](#tomba-enrichment).

```text
tomba enrich --target <email> [--enrich-mobile]
```

| Flag              | Short | Type   | Default | Description                                                                                           |
| ----------------- | ----- | ------ | ------- | ----------------------------------------------------------------------------------------------------- |
| `--target`        | `-t`  | string | —       | Email address. Required.                                                                              |
| `--enrich-mobile` | —     | bool   | `false` | Also return the person's phone number. Phone data changes the [cost](/usage-and-quotas#credit-costs). |

```bash
tomba enrich --target jane.doe@stripe.com
tomba enrich --target jane.doe@stripe.com --enrich-mobile --json
```

## `tomba enrichment`

Get a person profile, a company profile, or both. Each subcommand takes its input with `--target` and has no other flags.

```text
tomba enrichment person --target <email>
tomba enrichment company --target <domain>
tomba enrichment combined --target <email>
```

### `tomba enrichment person`

Get the profile of the person who owns an email address. Calls [`GET /v1/people/find`](/api/enrichment#person-api).

```bash
tomba enrichment person --target jane.doe@stripe.com
```

### `tomba enrichment company`

Get the profile of the company behind a domain. Calls [`GET /v1/companies/find`](/api/enrichment#company-api).

```bash
tomba enrichment company --target stripe.com
```

### `tomba enrichment combined`

Get the person and company profiles for an email address in one request. Calls [`GET /v1/combined/find`](/api/enrichment#combined-api).

```bash
tomba enrichment combined --target jane.doe@stripe.com --json
```

## `tomba verify`

Check whether an email address is deliverable. Calls [`GET /v1/email-verifier`](/api/verifier#email-verifier). For what the `status` and `result` values mean, see [Email verifier response](/attributes/verifier).

```text
tomba verify --target <email>
```

| Flag       | Short | Type   | Default | Description              |
| ---------- | ----- | ------ | ------- | ------------------------ |
| `--target` | `-t`  | string | —       | Email address. Required. |

```bash
tomba verify --target jane.doe@stripe.com
tomba verify --target jane.doe@stripe.com --json
```

For an address at a webmail or disposable email domain, the CLI prints a warning instead of the result, even with `--json`. The verification still runs and uses credits as usual.

## `tomba linkedin`

Find the email address for a LinkedIn profile. Calls [`GET /v1/linkedin`](/api/finder#linkedin-finder).

```text
tomba linkedin --target <profile URL> [--enrich-mobile]
```

| Flag              | Short | Type   | Default | Description                                                                                           |
| ----------------- | ----- | ------ | ------- | ----------------------------------------------------------------------------------------------------- |
| `--target`        | `-t`  | string | —       | LinkedIn profile URL. Required.                                                                       |
| `--enrich-mobile` | —     | bool   | `false` | Also return the person's phone number. Phone data changes the [cost](/usage-and-quotas#credit-costs). |

```bash
tomba linkedin --target "https://www.linkedin.com/in/jane-doe-example"
```

## `tomba sources`

List the public web pages where Tomba found an email address. Calls [`GET /v1/email-sources`](/api/email#email-sources).

```text
tomba sources --target <email>
```

| Flag       | Short | Type   | Default | Description              |
| ---------- | ----- | ------ | ------- | ------------------------ |
| `--target` | `-t`  | string | —       | Email address. Required. |

```bash
tomba sources --target jane.doe@stripe.com
```

## `tomba count`

Count the email addresses Tomba has for a domain, by department and seniority. Calls [`GET /v1/email-count`](/api/finder#email-count).

```text
tomba count --target <domain>
```

| Flag       | Short | Type   | Default | Description       |
| ---------- | ----- | ------ | ------- | ----------------- |
| `--target` | `-t`  | string | —       | Domain. Required. |

```bash
tomba count --target stripe.com
```

## `tomba status`

Check whether a domain belongs to a webmail or disposable email provider. Calls [`GET /v1/domain-status`](/api/domain#domain-status).

```text
tomba status --target <domain>
```

| Flag       | Short | Type   | Default | Description       |
| ---------- | ----- | ------ | ------- | ----------------- |
| `--target` | `-t`  | string | —       | Domain. Required. |

```bash
tomba status --target gmail.com
```

## `tomba format`

Get the email address patterns a domain uses, such as `{first}.{last}`. Calls [`GET /v1/email-format`](/api/finder#email-format).

```text
tomba format --target <domain>
```

| Flag       | Short | Type   | Default | Description       |
| ---------- | ----- | ------ | ------- | ----------------- |
| `--target` | `-t`  | string | —       | Domain. Required. |

```bash
tomba format --target stripe.com
```

## `tomba location`

Get a company's employee counts by location. Calls [`GET /v1/location`](/api/finder#location).

```text
tomba location --target <domain>
```

| Flag       | Short | Type   | Default | Description       |
| ---------- | ----- | ------ | ------- | ----------------- |
| `--target` | `-t`  | string | —       | Domain. Required. |

```bash
tomba location --target stripe.com
```

## `tomba autocomplete`

Suggest companies, with their domains and email counts, from part of a name. Calls [`GET /v1/domain-suggestions`](/api/domain-suggestions#get-domain-suggestions).

```text
tomba autocomplete --target <text>
```

| Flag       | Short | Type   | Default | Description                                            |
| ---------- | ----- | ------ | ------- | ------------------------------------------------------ |
| `--target` | `-t`  | string | —       | Company name or domain, complete or partial. Required. |

```bash
tomba autocomplete --target strip
```

## `tomba phone-finder`

Find phone numbers from an email address, a domain, or a LinkedIn profile. Calls [`GET /v1/phone-finder`](/api/phone#phone-finder).

```text
tomba phone-finder --email <email> [--full]
tomba phone-finder --domain <domain> [--full]
tomba phone-finder --linkedin <profile URL> [--full]
```

| Flag         | Short | Type   | Default | Description                                             |
| ------------ | ----- | ------ | ------- | ------------------------------------------------------- |
| `--email`    | —     | string | —       | Email address to look up.                               |
| `--domain`   | —     | string | —       | Domain to look up.                                      |
| `--linkedin` | —     | string | —       | LinkedIn profile URL to look up.                        |
| `--full`     | —     | bool   | `false` | Return every phone number found instead of one.         |
| `--target`   | `-t`  | string | —       | Used as `--email` when none of the three inputs is set. |

Pass one input. If you pass more than one, the CLI sends only the first of `--email`, `--domain`, and `--linkedin`. The input type affects the [cost](/usage-and-quotas#credit-costs).

```bash
tomba phone-finder --email jane.doe@stripe.com
tomba phone-finder --domain stripe.com --full
tomba phone-finder --linkedin "https://www.linkedin.com/in/jane-doe-example"
```

## `tomba phone-validator`

Check whether a phone number is valid, and get its formats, line type, and carrier. Calls [`GET /v1/phone-validator`](/api/phone#phone-validator).

```text
tomba phone-validator --phone <number> [--country-code <code>]
```

| Flag             | Short | Type   | Default | Description                                                                                       |
| ---------------- | ----- | ------ | ------- | ------------------------------------------------------------------------------------------------- |
| `--phone`        | —     | string | —       | Number to validate, in international format or, with `--country-code`, in local format. Required. |
| `--country-code` | —     | string | —       | Two-letter country code for parsing a local number, such as `US`.                                 |

```bash
tomba phone-validator --phone "+14155552671"
tomba phone-validator --phone 4155552671 --country-code US
```

## `tomba reveal`

Search for companies with a natural-language query or with filters. Calls [`POST /v1/reveal/search`](/api/reveal#search-companies).

```text
tomba reveal --query "<description>" [--page <n>]
tomba reveal [filter flags] [--page <n>]
```

Use `--query` or filter flags, not both: the API rejects a request that has both. Each filter flag takes a comma-separated list, or you can repeat the flag; the CLI sends the values as `include` filters. Accepted values are listed in [Search Companies](/api/reveal#search-companies).

| Flag             | Short | Type    | Default | Description                                                                  |
| ---------------- | ----- | ------- | ------- | ---------------------------------------------------------------------------- |
| `--query`        | `-q`  | string  | —       | Description of the companies to find, such as `Fintech companies in France`. |
| `--page`         | —     | int     | `1`     | Page of results.                                                             |
| `--country`      | —     | strings | —       | Country codes (ISO 3166-1 alpha-2), such as `US,GB`.                         |
| `--state`        | —     | strings | —       | States or regions.                                                           |
| `--city`         | —     | strings | —       | Cities.                                                                      |
| `--industry`     | —     | strings | —       | Industries.                                                                  |
| `--size`         | —     | strings | —       | Employee-count ranges, such as `51-200`.                                     |
| `--type`         | —     | strings | —       | Company types.                                                               |
| `--keywords`     | —     | strings | —       | Keywords.                                                                    |
| `--founded`      | —     | strings | —       | Founding-year ranges.                                                        |
| `--technologies` | —     | strings | —       | Technologies the company uses.                                               |
| `--similar`      | —     | strings | —       | Domains of companies to find look-alikes of.                                 |
| `--revenue`      | —     | strings | —       | Revenue ranges.                                                              |
| `--sic`          | —     | strings | —       | SIC codes.                                                                   |
| `--naics`        | —     | strings | —       | NAICS codes.                                                                 |

```bash
tomba reveal --query "Fintech companies in France"
tomba reveal --country US,GB --size 51-200,201-500
tomba reveal --country FR --size 51-200 --page 2 --json
```

On the Free plan, company search returns only the first page and ignores some filters; see [Free plan limits](/usage-and-quotas#free-plan-limits).

## `tomba similar`

Find companies similar to a domain. Calls [`GET /v1/similar`](/api/domain#similar).

```text
tomba similar --target <domain>
```

| Flag       | Short | Type   | Default | Description       |
| ---------- | ----- | ------ | ------- | ----------------- |
| `--target` | `-t`  | string | —       | Domain. Required. |

```bash
tomba similar --target stripe.com
```

## `tomba technology`

List the technologies detected on a domain's website. Calls [`GET /v1/technology`](/api/domain#technology).

```text
tomba technology --target <domain>
```

| Flag       | Short | Type   | Default | Description       |
| ---------- | ----- | ------ | ------- | ----------------- |
| `--target` | `-t`  | string | —       | Domain. Required. |

```bash
tomba technology --target stripe.com
```

## `tomba flag`

Report data from Tomba that's wrong, such as an address that bounced, and list your reports. Some confirmed reports return a credit; see [Refunds for incorrect data](/usage-and-quotas#refunds-for-incorrect-data).

### `tomba flag create`

Report an item. Calls [`POST /v1/flag`](/api/flag#flag-incorrect-data).

```text
tomba flag create --type <type> --value <item> --reason <reason> [--comment <text>]
```

| Flag        | Short | Type   | Default | Description                                                                                            |
| ----------- | ----- | ------ | ------- | ------------------------------------------------------------------------------------------------------ |
| `--type`    | —     | string | —       | Kind of item: `email`, `organization`, `phone`, `author_url`, or `website`. Required.                  |
| `--value`   | —     | string | —       | The item: an email address, domain, phone number, or URL. Required.                                    |
| `--reason`  | —     | string | —       | Why it's wrong. The valid reasons depend on `--type`; `tomba flag create --help` lists them. Required. |
| `--comment` | —     | string | —       | Optional details.                                                                                      |

```bash
tomba flag create --type email --value jane.doe@stripe.com --reason hard_bounce
tomba flag create --type phone --value "+14155552671" --reason wrong_phone --comment "Number disconnected"
```

### `tomba flag list`

List your reports and their review status. Calls [`GET /v1/flag`](/api/flag#list-my-flags). The text output leaves the reported item blank; use `--json`.

| Flag      | Short | Type | Default | Description       |
| --------- | ----- | ---- | ------- | ----------------- |
| `--page`  | —     | int  | `1`     | Page of results.  |
| `--limit` | —     | int  | `10`    | Reports per page. |

```bash
tomba flag list --json
```

## `tomba lead`

Manage the leads saved in your account. Get lead IDs from `tomba lead list --json`.

```text
tomba lead list [--page <n>] [--limit <n>]
tomba lead get --id <id>
tomba lead create --email <email> --list-id <id> [--first-name <name>] [--last-name <name>]
tomba lead update --id <id> [--email <email>] [--first-name <name>] [--last-name <name>]
tomba lead delete --id <id>
```

### `tomba lead list`

List leads, newest first. Calls [`GET /v1/leads`](/api/leads#retrieve-leads).

| Flag       | Short | Type   | Default | Description                                            |
| ---------- | ----- | ------ | ------- | ------------------------------------------------------ |
| `--page`   | —     | int    | `1`     | Page of results.                                       |
| `--limit`  | —     | int    | `10`    | Leads per page.                                        |
| `--domain` | —     | string | —       | Has no effect: the API doesn't filter leads by domain. |

### `tomba lead get`

Get one lead. Calls [`GET /v1/leads/{id}`](/api/leads#retrieve-a-single-lead). Requires `--id`.

### `tomba lead create`

Save a lead. Calls [`POST /v1/leads`](/api/leads#create-a-lead).

| Flag           | Short | Type   | Default | Description                                                    |
| -------------- | ----- | ------ | ------- | -------------------------------------------------------------- |
| `--email`      | —     | string | —       | Email address. Required.                                       |
| `--list-id`    | —     | string | —       | Lead list ID. Required by the CLI, but not applied: see below. |
| `--first-name` | —     | string | —       | First name.                                                    |
| `--last-name`  | —     | string | —       | Last name.                                                     |

The CLI sends `--list-id` as a string, which the API doesn't accept as a list ID, so the lead is saved without a list. To add a lead to a list, use the dashboard or [`POST /v1/leads`](/api/leads#create-a-lead) with a numeric `list_id`.

```bash
tomba lead create --email jane.doe@stripe.com --list-id 1 --first-name Jane --last-name Doe
```

### `tomba lead update`

Change a lead's email address or name. Calls [`PUT /v1/leads/{id}`](/api/leads#update-a-lead).

| Flag           | Short | Type   | Default | Description        |
| -------------- | ----- | ------ | ------- | ------------------ |
| `--id`         | —     | string | —       | Lead ID. Required. |
| `--email`      | —     | string | —       | New email address. |
| `--first-name` | —     | string | —       | New first name.    |
| `--last-name`  | —     | string | —       | New last name.     |

### `tomba lead delete`

Delete a lead. Calls [`DELETE /v1/leads/{id}`](/api/leads#delete-a-lead). Requires `--id`.

## `tomba leads-list`

Manage lead lists. Get list IDs from `tomba leads-list list --json`.

```text
tomba leads-list list
tomba leads-list get --id <id>
tomba leads-list create --name <name>
tomba leads-list update --id <id> --name <name>
tomba leads-list delete --id <id>
```

### `tomba leads-list list`

List your lead lists. Calls [`GET /v1/leads_lists`](/api/lead-lists#retrieve-leads-lists). Takes no flags.

### `tomba leads-list get`

Get one list. Calls [`GET /v1/leads_lists/{id}`](/api/lead-lists#retrieve-a-single-leads-list). Requires `--id`.

### `tomba leads-list create`

Create a list. Calls [`POST /v1/leads_lists`](/api/lead-lists#create-leads-list). Requires `--name`.

```bash
tomba leads-list create --name "Q3 prospects"
```

### `tomba leads-list update`

Rename a list. Calls [`PUT /v1/leads_lists/{id}`](/api/lead-lists#update-leads-list). Requires `--id` and `--name`.

### `tomba leads-list delete`

Delete a list. Calls [`DELETE /v1/leads_lists/{id}`](/api/lead-lists#delete-leads-list). Requires `--id`.

## `tomba attribute`

Manage custom lead attributes. Get attribute IDs from `tomba attribute list --json`.

```text
tomba attribute list
tomba attribute get --id <id>
tomba attribute create --name <name> --type <type>
tomba attribute delete --id <id>
```

### `tomba attribute list`

List your custom attributes. Calls [`GET /v1/attributes`](/api/lead-attributes#retrieve-lead-attributes). Takes no flags.

### `tomba attribute get`

Get one attribute. Calls [`GET /v1/attributes/{id}`](/api/lead-attributes#retrieve-a-single-lead-attribute). Requires `--id`.

### `tomba attribute create`

Create an attribute. Calls [`POST /v1/attributes`](/api/lead-attributes#create-a-lead-attribute). Requires `--name` and `--type`; the accepted types are listed in [Create a Lead Attribute](/api/lead-attributes#create-a-lead-attribute).

```bash
tomba attribute create --name "Company size" --type string
```

### `tomba attribute update`

Calls [`PUT /v1/attributes/{id}`](/api/lead-attributes#update-a-lead-attribute) with `--id` and `--name`. The API also requires the attribute's `type`, which the CLI doesn't send, so this subcommand fails with `error: 422 Unprocessable Entity`. Rename attributes in the dashboard or with the API.

### `tomba attribute delete`

Delete an attribute. Calls [`DELETE /v1/attributes/{id}`](/api/lead-attributes#delete-a-lead-attribute). Requires `--id`.

## `tomba key`

Manage the API keys of your workspace. For how keys expire and how to replace them, see [Key expiry](/authentication#key-expiry) and [Rotate keys](/authentication#rotate-keys). Get key IDs from `tomba key list --json`.

```text
tomba key list
tomba key get --id <id>
tomba key create
tomba key delete --id <id>
```

### `tomba key list`

List the keys of every member of your workspace. Calls [`GET /v1/keys`](/api/keys#retrieve-api-keys). The text output shortens each key; `--json` shows full values, IDs, and expiry dates.

### `tomba key get`

Get one key. Calls [`GET /v1/keys/{id}`](/api/keys#retrieve-a-single-api-key). Requires `--id`.

### `tomba key create`

Create a key with a generated name and the default lifetime. Calls [`POST /v1/keys`](/api/keys#create-an-api-key). The text output shows only the new key's ID; run `tomba key create --json` to get the key itself, in `data.message`. The command takes no flags; to set a name or a shorter lifetime, use the dashboard or the API.

### `tomba key delete`

Delete a key. Calls [`DELETE /v1/keys/{id}`](/api/keys#delete-an-api-key). Requires `--id`. Requests that use the key fail from then on, including the CLI's own if you logged in with that key.

### `tomba key reset`

Calls `PUT /v1/keys/{id}/reset`, a route the API doesn't have, so it fails with `error: 404 Not Found`. To rotate a key, use the dashboard or [`PUT /v1/keys/{id}`](/api/keys#reset-an-api-key).

## `tomba whoami`

Show the account the CLI is signed in to. Calls [`GET /v1/me`](/api/account#get-account).

```bash
tomba whoami
tomba whoami --json
```

The text output shows your account details and plan name. `--json` adds your search and verification allowances and usage, in `requests.domains` and `requests.verifications` ([Check usage](/usage-and-quotas#check-usage)), and your API secret, in `secret_token`. Don't share `--json` or `--output` output from this command.

## `tomba usage`

Show your daily usage. Calls [`GET /v1/usage`](/api/account#retrieve-api-usage).

```bash
tomba usage
```

The CLI keeps only the verification counts from the response; search and other counts show as `0`. For your balances, use `tomba whoami --json`, the [Usage](https://app.tomba.io/usage) page of the dashboard, or [`GET /v1/usage`](/api/account#retrieve-api-usage).

## `tomba logs`

Show your 20 most recent logged requests, newest first. Calls [`GET /v1/logs`](/api/account#retrieve-api-logs). Only charged lookups are logged, including repeats charged `0`; see [Duplicate requests](/usage-and-quotas#duplicate-requests). The text output lists each request's method, URI, type, and date; `--json` adds its cost.

```bash
tomba logs
tomba logs --json
```

The command takes no paging flags. To page through older entries, call [`GET /v1/logs`](/api/account#retrieve-api-logs) with `page` and `limit`.