Lead research API

Research leads before your team touches the account.

Huntr turns a company, domain, or person prompt into usable lead context: role notes, company fit, buying signals, outreach angles, and CRM-ready summaries.

Get API key View API reference

Job

Turn a lead and account into sales-ready context

Best fit

Outbound prep, CRM notes, lead routing, agency QA

Operator

SDR teams, founders, RevOps, outbound agencies

Output

Role context, account fit, risks, and outreach angle

What lead research should answer

A lead research API should not just decorate a contact record. It should help a rep or automation decide whether the person is worth contacting, what business context matters, and what should be reviewed before outreach.

Why this person?

Role relevance, responsibility area, seniority context, and whether the person likely owns or influences the workflow.

Why this company?

Account fit, business model, public context, and whether the company looks like a real opportunity.

Why now?

Signals that suggest urgency: hiring, expansion, product changes, funding, partnerships, or visible operational shifts.

What should we say?

A grounded outreach angle, plus uncertainty notes so the team does not overstate weak evidence.

Lead research request

POST /researchLead context prompt

curl https://api.tryhuntr.com/research \
  -H "x-api-key: hntr_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tier": "standard",
    "prompt": "Research the Head of RevOps at Ramp. Return role context, company priorities, likely pain points, and a concise outbound angle."
  }'

Representative output

Lead briefExample shape

{
  "lead_context": "The person appears responsible for revenue operations, sales systems, routing, and data quality.",
  "account_fit": "The company has a high-volume sales motion where research quality can affect outbound conversion.",
  "relevant_signals": ["recent GTM hiring", "public focus on automation", "expanding sales operations"],
  "outreach_angle": "Frame the conversation around reducing manual account research before reps enroll leads.",
  "review_notes": "Do not claim budget or active evaluation unless confirmed by the seller."
}

How teams operationalize it

Outbound teams

Call Huntr after list building and before enrollment. Store the result as a rep review note or personalization input.

RevOps teams

Write lead research into CRM fields used for routing, QA, account review, and sales manager visibility.

Agencies

Turn campaign research into a repeatable production step instead of asking contractors to manually browse each account.

Founder-led sales

Prep high-intent leads before manual outreach, demos, or partner conversations without building a research workflow from scratch.

Prompts by workflow

Outbound prep

Research this lead and company. Return role context, account fit, likely priorities, and the safest outreach angle.

CRM note

Create a CRM-ready lead note with company context, role relevance, public signals, risks, and next best action.

Lead routing

Evaluate whether this lead should be routed to sales. Return fit evidence, disqualifiers, missing information, and review notes.

Agency QA

Research this prospect for a client campaign. Return message angle, weak assumptions, and what a human should verify before launch.

When not to use a lead research API

Cold list hygiene only

If you only need email verification, deduping, or field normalization, use a dedicated data-cleaning workflow instead.

Fully automated sending without review

Huntr can produce research context, but outreach copy and claims should still go through your approval process before campaigns run.

FAQ

Can Huntr write personalization lines?

It can return the research context and angle that personalization depends on. Teams should still review final outbound copy before sending.

Can this work with Aimfox or Smartlead?

Yes. Run Huntr before enrollment, then pass the research note or structured fields into your outbound workflow.

Is this enrichment?

It is adjacent to enrichment, but the core job is different: lead research explains context and relevance, not just fixed fields.

Claygent Alternative Claygent API Lead Research API Company Research API AI GTM Research API Pricing