Copy page

Apify

Apify

Tomba publishes 15 actors on the Apify Store under the tomba-io account. Each actor runs one Tomba lookup over a list of inputs and stores the results in a dataset; the actor reference lists their inputs and outputs. Tomba builds and maintains the actors.

Prerequisites

• An Apify account. You don't need a Tomba account or API key: the actors call Tomba with Tomba's own credentials.
• To start runs through the API or call the real-time API, an Apify API token, from Settings > API & Integrations in Apify Console.

Costs

Apify charges your Apify account per event; the event price is on each actor's Store page. Tomba doesn't charge you anything.

• Each request charges one tomba-request event per Tomba credit it costs. The credits per request, including the extra credits for phone data, are the ones in Credit costs. Technology finder charges one event per domain with technologies.
• A request is charged only when Tomba returns a result, including a negative answer such as an undeliverable verification or a domain with no email addresses.
• Error statuses, empty results, responses with an errors object, and results served from the actor's cache are free.

Each dataset item has a charged field, and chargedCredits where a request can cost more than one credit. To cap a run's cost, set Max cost per run in the run options; the actor stops when it reaches the cap.

Run an actor

The actors run with limited permissions, so they need no approval before the first run.

• Console: open the actor, fill in the input form, and select Start. Results appear in the run's default dataset as they arrive, and you can export them from the run page.
• API: send the input as JSON to the actor's run endpoint, using the actor ID with a ~ in place of the /. See the example.
• Schedule: in Schedules, create a schedule with a cron expression and add the actor, or a saved task with its input. Apify schedules an actor only after it has run at least once.
• Real-time API: call the actor's Standby URL to get results in the HTTP response instead of a dataset. See Real-time API.

Actors

Person, Company, and Combined enrichment return Tomba's data in a Clearbit-compatible format, which is why their actor IDs start with clearbit-.

Example

Search stripe.com with the Domain search actor and get the dataset in the same call:

Code
curl -X POST "https://api.apify.com/v2/actors/tomba-io~domain-search/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains": ["stripe.com"], "limit": "10"}'

The response is a JSON array with one item per domain, each holding organization and emails. This endpoint waits at most 300 seconds for the run. For longer runs, start the run with POST /v2/actors/tomba-io~domain-search/runs and read its dataset when it finishes.

Real-time API

Every actor also runs in Apify Standby mode, an HTTP server that returns results in the response. Find the actor's Standby URL and its OpenAPI description on the actor's API tab, and authenticate with your Apify API token.

Code
curl "https://<standby-url>/?domain=stripe.com" \
  -H "Authorization: Bearer $APIFY_TOKEN"

• GET / with query parameters runs one lookup; each actor's query parameters are in the actor reference.
• POST / with the same JSON input as a run processes a list.
• The response is {"items": [...]}, with the same items as the dataset. Costs are the same as for a run.

Troubleshooting