Company Enrichment

When you already have a domain or LinkedIn URL, direct company endpoints return deterministic data faster than /research.

Endpoints

Endpoint	Returns
`POST /company-linkedin`	Company profile from LinkedIn
`POST /company-linkedin-url`	Resolve LinkedIn company URL from domain
`POST /company-linkedin-posts`	Recent posts from a LinkedIn company page
`POST /company-tech-stack`	Detected technologies
`POST /company-contact`	Emails, phones, social profiles from website
`POST /company-jobs`	Active job listings

Tech stack

curl --request POST \
  --url https://api.tryhuntr.com/company-tech-stack \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{ "domain": "linear.app" }'

LinkedIn company profile

curl --request POST \
  --url https://api.tryhuntr.com/company-linkedin \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{ "linkedin_url": "https://www.linkedin.com/company/linearapp" }'

Site contacts

Extracts emails, phones, and social links from the company website:

curl --request POST \
  --url https://api.tryhuntr.com/company-contact \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{ "domain": "notion.so" }'

Charged when emails or phones are found; free when neither is found.

LinkedIn company posts

curl --request POST \
  --url https://api.tryhuntr.com/company-linkedin-posts \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "linkedin_url": "https://www.linkedin.com/company/stripe"
  }'

Each page contains up to 10 posts. When pagination.token is not null, pass it back with the same company URL:

{
  "linkedin_url": "https://www.linkedin.com/company/stripe",
  "pagination": {
    "token": "TOKEN_FROM_PREVIOUS_RESPONSE"
  }
}

Stop when pagination.token is null. Tokens are opaque and must not be modified or reused with another company.

Job listings

curl --request POST \
  --url https://api.tryhuntr.com/company-jobs \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{ "domain": "vercel.com" }'

Useful for hiring signals and outreach timing.

Chain enrichment in automations

Typical Clay or n8n column order:

company-linkedin-url — resolve URL from domain
company-linkedin — firmographics
company-linkedin-posts — announcements and engagement signals
company-tech-stack — stack fit scoring
company-jobs — hiring signal
person-search → person-email — find buyers

When to use `/research` instead

Use /research when you need synthesis — e.g. “Summarize partnership angles given their stack, hiring, and recent announcements.” Use direct endpoints when you need raw fields for scoring or CRM columns.

Getting started

Concepts

Guides

Build with AI

Integrations

Reference

Company Enrichment

Endpoints

Tech stack

LinkedIn company profile

Site contacts

LinkedIn company posts

Job listings

Chain enrichment in automations

When to use `/research` instead

Next step

​Endpoints

​Tech stack

​LinkedIn company profile

​Site contacts

​LinkedIn company posts

​Job listings

​Chain enrichment in automations

​When to use /research instead

​Next step

Endpoints

Tech stack

LinkedIn company profile

Site contacts

LinkedIn company posts

Job listings

Chain enrichment in automations

When to use `/research` instead

Next step