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
Information
Finder
Verifier
Enrichment
Phone
Domain
Email
Domain Suggestions
Reveal
Bulks
Scrape Campaigns
Leads
Lead Lists
Lead Attributes
Account
Keys
    Retrieve API KeysgetCreate an API KeypostRetrieve a Single API KeygetReset an API KeyputDelete an API KeydeleteRename an API Keypatch
Flag
MCP Server
Schemas
Tomba
Tomba

Keys

Download schema

Create, rotate, and delete API keys


Retrieve API Keys

GET
https://api.tomba.io/v1
/keys
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns the API keys of your workspace: yours and every other member's, including their full key values. Without a workspace, returns your own keys. The response holds at most 50 keys, oldest first.

Limited to 100 requests per minute. Also accepts an OAuth 2.0 access token with the account scope.

Retrieve API Keys › Responses

The keys of your workspace. Each key still authenticates as its own owner, and its requests are charged to that owner.

​object · required
GET/keys
curl https://api.tomba.io/v1/keys \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "keys": [ { "id": 17, "user_id": 1042, "key": "ta_xxxx", "name": "CI runner", "ip": "203.0.113.42", "expires_at": "2027-01-15T08:00:00Z", "created_by": 1042, "last_used_at": "2026-09-28T14:22:00Z", "created_at": "2026-01-15T08:00:00Z", "updated_at": "2026-01-15T08:00:00Z", "is_owner": true, "expired": false, "expires_in_days": 108, "creator_name": "Jane Doe", "creator_email": "jane.doe@stripe.com" }, { "id": 23, "user_id": 2087, "key": "ta_yyyy", "name": "Zapier", "ip": "198.51.100.7", "expires_at": "2027-06-01T10:30:00Z", "created_by": 2087, "last_used_at": "2026-09-27T09:15:00Z", "created_at": "2026-06-01T10:30:00Z", "updated_at": "2026-06-01T10:30:00Z", "is_owner": false, "expired": false, "expires_in_days": 245, "creator_name": "John Smith", "creator_email": "john.smith@stripe.com" } ] } }
json
application/json

Create an API Key

POST
https://api.tomba.io/v1
/keys
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Creates an API key for your account and returns its value in data.message. The request body is optional:

  • Without name, the key is named Default key, or Default key 2, Default key 3, and so on when that name is taken.
  • Without expires_in_days, the key expires in 365 days, the maximum.

You can hold as many unexpired keys as pricing.available_keys in GET /me, and at least 25 while you have unused credit-pack credits. Expired keys don't count. Past the limit, the request fails with 422 rate_limit.

Tomba emails you when a key is created. Limited to 100 requests per hour. Also accepts an OAuth 2.0 access token with the account scope. See Rotate keys.

Create an API Key › Request Body optional

name
​string · minLength: 2 · maxLength: 100

Label for the key, 2 to 100 characters after trimming spaces. Name the key after where it will be used.

expires_in_days
​integer · min: 1 · max: 365

Key lifetime in days, from 1 to 365.

Default: 365

Create an API Key › Responses

Key created.

​object · required
POST/keys
curl https://api.tomba.io/v1/keys \ --request POST \ --header 'Content-Type: application/json' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>' \ --data '{ "name": "billing-service", "expires_in_days": 90 }'
Example Request Body
{ "name": "billing-service", "expires_in_days": 90 }
json
application/json
Example Responses
{ "data": { "id": 1234, "message": "ta_xxxx" } }
json
application/json

Retrieve a Single API Key

GET
https://api.tomba.io/v1
/keys/{keyId}
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns one API key of your workspace, including its value. After rotating a key with PUT, read its new value here.

Limited to 100 requests per minute for each key ID. Also accepts an OAuth 2.0 access token with the account scope.

Retrieve a Single API Key › path Parameters

keyId
​integer · int64 · required

The key's ID. A non-numeric ID fails with 422.

Retrieve a Single API Key › Responses

The key.

​object · required
GET/keys/{keyId}
curl https://api.tomba.io/v1/keys/:keyId \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "keys": { "id": 17, "user_id": 1042, "key": "ta_xxxx", "name": "CI runner", "ip": "203.0.113.42", "expires_at": "2027-01-15T08:00:00Z", "created_by": 1042, "last_used_at": "2026-09-28T14:22:00Z", "created_at": "2026-01-15T08:00:00Z", "updated_at": "2026-01-15T08:00:00Z", "is_owner": true, "expired": false, "expires_in_days": 108, "creator_name": "Jane Doe", "creator_email": "jane.doe@stripe.com" } } }
json
application/json

Reset an API Key

PUT
https://api.tomba.io/v1
/keys/{keyId}
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Rotates a key: issues a new value and a new 365-day expiry, and the old value stops working immediately. The key keeps its ID, name, and creator. Rotating also revives an expired key.

The response doesn't include the new value; read it with GET /keys/{keyId}. Any member of the key owner's workspace can rotate the key. Limited to 100 requests per hour for each key ID. Also accepts an OAuth 2.0 access token with the account scope.

Reset an API Key › path Parameters

keyId
​integer · int64 · required

The key's ID. A non-numeric ID fails with 422.

Reset an API Key › Responses

Key rotated.

OperationSuccess
​object · required

Result of an update or delete.

PUT/keys/{keyId}
curl https://api.tomba.io/v1/keys/:keyId \ --request PUT \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "status": true, "message": "The API key has been reset and expires in a year.", "code": 200 } }
json
application/json

Delete an API Key

DELETE
https://api.tomba.io/v1
/keys/{keyId}
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Deletes a key. Requests made with it fail from then on.

Any member of the key owner's workspace can delete the key. Limited to 100 requests per hour for each key ID. Also accepts an OAuth 2.0 access token with the account scope.

Delete an API Key › path Parameters

keyId
​integer · int64 · required

The key's ID. A non-numeric ID fails with 422.

Delete an API Key › Responses

Key deleted.

OperationSuccess
​object · required

Result of an update or delete.

DELETE/keys/{keyId}
curl https://api.tomba.io/v1/keys/:keyId \ --request DELETE \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "status": true, "message": "The keys has been delete successfully.", "code": 200 } }
json
application/json

Rename an API Key

PATCH
https://api.tomba.io/v1
/keys/{keyId}
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Changes a key's name. The name is the only field you can edit. Expiry can't be changed: to extend a key, rotate it with PUT, which issues a new value with a new 365-day term.

Any member of the key owner's workspace can rename the key. Limited to 100 requests per hour for each key ID. Also accepts an OAuth 2.0 access token with the account scope.

Rename an API Key › path Parameters

keyId
​integer · int64 · required

The key's ID. A non-numeric ID fails with 422.

Rename an API Key › Request Body

name
​string · minLength: 2 · maxLength: 100 · required

New name for the key, 2 to 100 characters after trimming spaces.

Rename an API Key › Responses

Key renamed.

OperationSuccess
​object · required

Result of an update or delete.

PATCH/keys/{keyId}
curl https://api.tomba.io/v1/keys/:keyId \ --request PATCH \ --header 'Content-Type: application/json' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>' \ --data '{ "name": "CI runner v2" }'
Example Request Body
{ "name": "CI runner v2" }
json
application/json
Example Responses
{ "data": { "status": true, "message": "The API key has been renamed.", "code": 200 } }
json
application/json

AccountFlag