Overview

People Search provides gated, Apollo-style lead discovery over approved Lempile people snapshots. It returns only safe search metadata plus contact availability. Raw email and phone values are handled by the separate People Reveal API.

Quick Start#

curl -sS -X POST "https://api.lempile.com/people/search" \
  -H "X-API-KEY: $LEMPILE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "person_countries": ["Canada"],
    "job_titles": ["sales"],
    "company_employee_ranges": [{ "min": 101, "max": 200 }],
    "has_email": true,
    "facets": ["person_country", "seniority", "company_size"],
    "page": 1,
    "per_page": 25
  }'

The route requires people.read. Contact reveal requires people.reveal on the separate /people/reveal route.

Response#

{
  "object": "people_search_result",
  "total": 0,
  "page": 1,
  "per_page": 25,
  "has_more": false,
  "data": [],
  "facets": {
    "person_country": {},
    "seniority": {},
    "company_size": {}
  }
}

Each result contains person role/location fields, company metadata, LinkedIn URL when available, and contact availability/status. Search does not return raw emails or raw phone numbers.

Filters#

• person_countries: exact country names.
• person_locations: text match over city, state, country, and location label.
• job_titles: text match over title, normalized title, and function.
• seniorities: exact seniority labels.
• company_domains: normalized company domains.
• company_employee_ranges: objects with min and/or max.
• company_industries: text match over company industry.
• email_statuses: exact email status labels.
• has_email: boolean.
• page: 1 to 500.
• per_page: 1 to 100.

Supported facets are person_country, seniority, company_size, company_industry, email_status, and has_email.

Gated Data Policy#

Default API calls only search active snapshots whose provenance has been approved. The Apollo_BF archive is not exposed by this API. Platform admins can request synthetic QA sample records with "sample": true; non-admin keys receive 403 for sample mode.

Real imports are controlled through the internal People Import Gate. A platform admin must register source provenance, confirm lawful use, approve the source, run a capped local-file import, and activate the resulting snapshot before it is visible to this API. See people-imports.md.