“Do a deep search on all the API searches for people.”
A deep scan as of 7 September 2026 catalogued 293 API endpoint-or-family rows from 31 normalized providers across 33 first-party documentation hosts, sorted into 13 categories. It is a broad market inventory, not a provably exhaustive census: no canonical registry exists, product naming varies, and some sales-gated products publish little documentation. Three categories dominate — person enrichment (87 rows), people search (72) and platform user/profile APIs (69) — yet “people API” is not one market: professional enrichment, platform-native lookup, identity/public-record resolution and consent-based screening carry fundamentally different permissible uses.
B2B prospecting and recruiting: Lusha, RocketReach, Proxycurl, Apollo, Crustdata, FullContact, People Data Labs, Hunter, Snov.io, Coresignal, Dropcontact. Inputs are names, domains and profile URLs; outputs are work emails, phones and employment history.
Data confined to that platform and its permission model: X, TikTok, GitHub, Meta/Instagram/Threads, Twitch, Microsoft. Free of per-call pricing but bound by scopes, tokens and app review.
Fraud checks and contact validation: Trestle, Whitepages, Twilio, Truecaller, Pipl. Phone or email in; owner name, line type and trust scores out.
Only in compliant consent-based workflows: Checkr, Accurate, GoodHire, Entrust/Onfido. In the US these are FCRA consumer-report workflows requiring candidate consent and permissible purpose.
| Provider | Product | Category | Inputs | Outputs | Pricing | Access / compliance | Source |
|---|
Blank cells mean the source page did not state the value. Rows marked “verify” document neither inputs nor outputs and need reader verification before use.
Method: inventory of 293 API endpoint-or-family rows about searching, matching, enriching, verifying or screening individual people, extracted 2026-09-07 from first-party documentation and product pages of 31 normalized providers on 33 hosts; the largest single URL supports 7/293 rows (2.4%). Counts measure documented endpoint/family rows, not market share; extraction can split one API family into several rows. Long input/output/pricing text is truncated for space. Pricing changes quickly and often requires sales contact; check each provider's current terms, privacy-law obligations, platform policy and permitted use before implementation.