The Hog gives you two complementary ways to work with people data. First, use the people search endpoint to find contacts using a natural language query — optionally scoped to a specific company or filtered by title and location. Then, for any contact you want to understand more deeply, use the people research endpoint to pull a cross-platform dossier using their social handles.Documentation Index
Fetch the complete documentation index at: https://docs.thehog.ai/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint overview
| Endpoint | Method | What it does |
|---|---|---|
/api/people/search | POST | Find ICP-matched people via NL query |
/api/people/researches | POST | Build a deep dossier via identity resolution |
People search
Use this endpoint to discover contacts that match a natural language description. Results are semantically ranked by ICP fit.Request fields
| Field | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Natural language description, e.g. "VP of Sales at a Series B SaaS company" |
titles | string[] | No | Exact or partial title filters (e.g. ["VP Sales", "Head of Revenue"]) |
locations | string[] | No | Location filters (e.g. ["New York", "London"]) |
companyId | string | No | Scope results to a specific company by its ID from company search |
personaId | string | No | Persona ID for semantic ICP matching |
projectId | string | No | Project context (can also be set via X-Project-Id header) |
maxResults | number | No | Maximum contacts to return; between 1 and 200 |
similarityThreshold | number | No | Semantic match cutoff between 0 and 1; higher values return closer matches only |
Examples
Response
The search returns HTTP200 with a data array of PersonCard objects.
People research
Once you have specific individuals in mind, use the research endpoint to build a richer cross-platform dossier. You supply one or more platform identities (LinkedIn, X, GitHub, etc.) and The Hog resolves them into a unified profile.This endpoint is synchronous but involves real-time data gathering, so expect response times of 2–30 seconds depending on how many identities are provided and which platforms are queried.
Request fields
| Field | Type | Required | Description |
|---|---|---|---|
identities | PlatformIdentity[] | Yes | One or more platform handles to resolve |
PlatformIdentity object has:
| Field | Type | Values |
|---|---|---|
platform | string | "linkedin", "x", "reddit", "github", "instagram", "tiktok" |
username | string | The platform handle or username |
Examples
Typical workflow
Search for target companies
Use
POST /api/companies/search with firmographic and signal filters to build your target account list. Note the id of each company you want to prospect.Find contacts at each account
Pass the company
id as companyId to POST /api/people/search along with a role-based query (e.g. "Head of Engineering") to surface relevant contacts.Research high-priority individuals
For contacts you want to engage, collect their social handles and send them to
POST /api/people/researches to get a cross-platform dossier.