Skip to content

Email for a named person at a company domain, with score.

This API endpoint finds the most likely email address from a domain name, a first name and a last name.

Job email.find

Your AI asks

choose input values first
telipot inspect hunter.email.find

Provider's rate

$0.0245 / email
Inspect· before choosing inputs

hunter.email.find

$0.0245 / emailYour plan

Whose account it uses

1The person asking
not needed
2Your company’s Hunter plan
Selected identity for this example
3Our account
not used

Choose inputs

domain · Company domain. Give domain, company or linkedin_handle. A URL or a leading @ is reduced to the domain.

company · Company name, used when the domain is unknown. A domain gives better results; domain wins when both are given.

No complete example input is recorded. Inspect reads the schema; it does not run the task.

What it costs

$0.0245

per email · billed on success

rate1 credit per email, billed on success
sourcedocs · help.hunter.io/en/articles/1911617-how-do-credits-work-in-hunter · checked 2026-10-05
confidencedocumented
noteAll-in-one plans: 1 credit per email found, none when no email is found, and a repeat of the same search in one billing period is not charged again. Data Platform plans: 1 Search credit per email.

For developers · inspect first

Read the schema and choose input values

telipot inspect hunter.email.find

No complete example input is recorded. Read the field notes below before building the call.

domain

string

Company domain. Give domain, company or linkedin_handle. A URL or a leading @ is reduced to the domain.

company

string

Company name, used when the domain is unknown. A domain gives better results; domain wins when both are given.

linkedin_handle

string

LinkedIn profile handle. With it no name is needed.

first_name

string

With last_name, required unless full_name or linkedin_handle is given.

last_name

string

With first_name, required unless full_name or linkedin_handle is given.

full_name

string

Required unless first_name and last_name, or linkedin_handle, is given. First and last name give better results.

max_duration

integer · 3 to 20 · default 10

Seconds the lookup may run. A longer time lets Hunter refine the result.

data

object

meta

object

Full output schema · JSONNested fields and constraints

Output JSON Schema

{
  "type": "object",
  "required": [
    "data",
    "meta"
  ],
  "properties": {
    "data": {
      "type": "object",
      "required": [
        "first_name",
        "last_name",
        "email",
        "score",
        "domain",
        "accept_all",
        "position",
        "linkedin_url",
        "company",
        "sources",
        "verification"
      ],
      "properties": {
        "first_name": {
          "type": [
            "string",
            "null"
          ]
        },
        "last_name": {
          "type": [
            "string",
            "null"
          ]
        },
        "email": {
          "type": [
            "string",
            "null"
          ]
        },
        "score": {
          "type": [
            "integer",
            "null"
          ],
          "description": "Estimated probability, 0 to 100, that the address is correct"
        },
        "domain": {
          "type": [
            "string",
            "null"
          ]
        },
        "accept_all": {
          "type": [
            "boolean",
            "null"
          ]
        },
        "position": {
          "type": [
            "string",
            "null"
          ]
        },
        "twitter": {
          "type": [
            "string",
            "null"
          ]
        },
        "linkedin_url": {
          "type": [
            "string",
            "null"
          ]
        },
        "phone_number": {
          "type": [
            "string",
            "null"
          ]
        },
        "company": {
          "type": [
            "string",
            "null"
          ]
        },
        "source_type": {
          "type": [
            "string",
            "null"
          ],
          "description": "found or generated"
        },
        "sources": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "domain": {
                "type": "string"
              },
              "uri": {
                "type": "string"
              },
              "extracted_on": {
                "type": "string"
              },
              "last_seen_on": {
                "type": "string"
              },
              "still_on_page": {
                "type": "boolean"
              }
            }
          }
        },
        "verification": {
          "type": "object",
          "properties": {
            "date": {
              "type": [
                "string",
                "null"
              ]
            },
            "status": {
              "type": [
                "string",
                "null"
              ],
              "description": "valid, accept_all or unknown"
            }
          }
        }
      }
    },
    "meta": {
      "type": "object",
      "properties": {
        "params": {
          "type": "object"
        }
      }
    }
  }
}

A real answer

No example captured yet: one is recorded when telipot catalog verify passes.