People & contact data API for AI assistants

The people and contact data API takes a job title, company name, location, or a combination of filters and returns a list of people who match. Each result includes the name, current role, company, email address, and LinkedIn profile link. Your assistant uses it to find the right person before sending an intro, to build a list of leads, or to check contact details before a call.

What it does

You pass search filters such as job title, seniority level, company domain, location, or company size. Providers accept different combinations: some take a natural language query, some let you filter by skills or education, and some restrict by revenue range or technology stack.

The API returns a list of matches, each with the person's name, current title, company, and location. Most providers include email addresses, LinkedIn profile URLs, and phone numbers when available. A few return extra fields like past employers, education, or social media links. The reply is JSON, so your assistant reads each field directly.

How a Joshu assistant uses it

When you ask Joshu to find decision makers at a list of target companies, it runs a people search for each domain with filters like "VP of Sales" or "Head of Marketing" and puts the results in a spreadsheet with contact details.

Before sending a cold email campaign, Joshu searches for people by role and location, checks which results have verified emails, and builds a list sorted by seniority.

When you hand Joshu a company domain and ask who to contact about a partnership, it pulls the list of executives and managers, reads their LinkedIn profiles, and drafts a short note on who handles the type of partnership you described.

Choosing a provider

Start with a provider that lets you filter by the fields you care about. If you search mostly by job title and company, pick one with those filters and a low per-record price. If you need natural language queries or advanced filters like technology stack or funding stage, use a provider that supports them.

Providers differ in which contact details they return. Some always include email addresses, some mark emails as verified or likely to engage, and a few offer phone numbers or social profiles. If email deliverability is critical, choose one that flags verification status.

A few providers charge per result returned, not per search. When the API bills by the record, set a page size or result limit to control the cost.

curl https://hello.joshu.me/api/router/call \
  -H "Authorization: Bearer $JOSHU_ROUTER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "endpoint": "aiark.people.search",
    "params": {
      "page": 0,
      "size": 1,
      "account": {
        "domain": {
          "any": {
            "include": [
              "example.com"
            ]
          }
        }
      }
    }
  }'