Response reference

Person response

Returned by GET /email-finder, GET /enrich, GET /linkedin, and GET /author-finder at data, and by GET /domain-search at data.emails[]. With full=true, the LinkedIn finder returns an array of people in data.

Fields

When a finder or enrichment request finds no address, data.email is null and the other fields are null, false, or 0. Domain search returns an empty data.emails array instead.

Field	Type	Returned by	Description
`email`	string or null	All	The email address.
`first_name`	string or null	All	First name.
`last_name`	string or null	All	Last name.
`full_name`	string or null	All	First and last name.
`gender`	string or null	All	`male` or `female`.
`country`	string or null	All	Two-letter country code (ISO 3166-1 alpha-2).
`position`	string or null	All	Job title.
`department`	string or null	All	See Departments. Empty or `null` when unknown.
`type`	string or null	All	`personal` or `generic`. See Email types.
`twitter`	string or null	All	Twitter (X) profile URL.
`linkedin`	string or null	All	LinkedIn profile URL.
`phone_number`	boolean	All	`true` when Tomba has a phone number for the person.
`score`	integer	All	Confidence from 0 to 100 that the address is correct, based on its last verification result and the number of public sources that list it.
`verification.status`	string or null	All	Result of Tomba's last check of the address: `valid`, `accept_all`, `invalid`, or `unknown`, with the meanings in Status values. `null` if Tomba hasn't checked it.
`verification.date`	string or null	All	When Tomba last checked the address, in RFC 3339 format.
`sources`	array	All	Public pages where the address appears. See Sources response.
`phone_data`	array	All but author finder	Phone numbers, when you set `enrich_mobile=true`. See Phone response.
`seniority`	string or null	Domain search	`junior`, `senior`, or `executive`.
`website_url`	string or null	Finders, enrichment	Company domain.
`company`	string or null	Finders, enrichment	Company name.
`pattern`	string or null	Finders, enrichment	Format of the address, such as `{first}.{last}`. See Patterns.
`accept_all`	boolean or null	Finders, enrichment	`true` when the domain accepts mail for any address (catch-all).
`disposable`, `webmail`	boolean	Email enrichment	Whether the address's domain is a disposable or webmail provider.
`info`	object	Author finder	The article and its author candidates. See Author finder.

Values

Email types

`type`	Meaning
`personal`	The address belongs to one person, such as `jane.doe@stripe.com`.
`generic`	A role address that a team shares, such as `support@stripe.com`.

Departments

accounting, administrative, communication, diversity, education, engineering, executive, facilities, finance, healthcare, hr, it, legal, management, marketing, operations, pr, sales, security, software, support, warehouse.

Domain search accepts the same values in its department parameter.

Author finder

GET /author-finder returns the fields above for the article's author, plus data.info with the article and every author candidate found on the page. info is also returned when no address is found, as long as the page could be read.

Field	Type	Description
`info.url`	string	The article URL.
`info.title`	string	Article title.
`info.description`	string	Article description.
`info.og_image`	string	URL of the article's Open Graph image.
`info.article_domain`	string	Domain that hosts the article.
`info.publisher_name`	string	Name of the publication.
`info.publish_date`	string	Publication date, as it appears on the page.
`info.candidates`	array	People named as the author on the page, best match first.

Each candidate has these fields. Fields other than the names, name_confidence, score, and count are left out when they're empty.

Field	Type	Description
`full_name`, `first_name`, `last_name`	string	The candidate's name.
`email`	string	Address published on the page for the candidate.
`job_title`	string	Job title from the page.
`bio`	string	Biography from the page.
`image`	string	URL of the candidate's picture.
`gravatar`	boolean	`true` when `image` comes from Gravatar.
`author_url`	string	The candidate's author page on the publication.
`website`	string	The candidate's own website.
`linkedin`, `twitter`, `facebook`, `github`, `instagram`, `youtube`, `mastodon`, `bluesky`	string	Handles of the candidate's profiles found on the page.
`sources`	array of strings	Where on the page the name was found, such as `json-ld`, `meta-author`, or `byline`.
`name_confidence`	number	Confidence from 0 to 1 that the text is a person's name.
`score`	number	Ranking score from 0 to 1. Candidates are sorted by it.
`count`	integer	How many times the name appears on the page.

Example

GET /email-finder?domain=stripe.com&first_name=Jane&last_name=Doe:


Code
{
    "data": {
        "email": "jane.doe@stripe.com",
        "first_name": "Jane",
        "last_name": "Doe",
        "full_name": "Jane Doe",
        "website_url": "stripe.com",
        "company": "Stripe",
        "pattern": "{first}.{last}",
        "department": "engineering",
        "type": "personal",
        "position": "Software Engineer",
        "country": "US",
        "gender": "female",
        "twitter": null,
        "linkedin": null,
        "score": 100,
        "accept_all": false,
        "phone_number": false,
        "verification": {
            "date": "2025-01-15T10:32:00+01:00",
            "status": "valid"
        },
        "sources": [
            {
                "uri": "https://stripe.com/blog/engineering",
                "website_url": "stripe.com",
                "extracted_on": "2024-06-01T09:14:07+01:00",
                "last_seen_on": "2025-01-10T17:02:44+01:00",
                "still_on_page": true
            }
        ],
        "phone_data": []
    }
}

Last modified on September 30, 2026

Data sources Company response