POST with JSON and an x-api-key header.
Common pattern
- Trigger — new row, form submit, CRM stage change
- HTTP Request — call a Huntr endpoint
- Map response — push fields to CRM, Slack, or spreadsheet
n8n
Use the HTTP Request node:| Setting | Value |
|---|---|
| Method | POST |
| URL | https://api.tryhuntr.com/research (or any endpoint) |
| Authentication | Header x-api-key |
| Body | JSON |
callback_url pointing to an n8n webhook trigger, or poll GET /research/{request_id}/status.
Make (Integromat)
Use the HTTP module with the same URL, headers, and JSON body. Map output fields from the response JSON.Zapier
Use Webhooks by Zapier → Custom Request, or a code step withfetch.
Suggested workflows
| Workflow | Endpoints |
|---|---|
| New account in CRM → enrich | company-linkedin → company-tech-stack → company-jobs |
| ICP list build weekly | company-search with pagination loop |
| Alert on hiring | company-jobs on watchlist domains |
| Pre-call brief | research tier standard or deep |
Rate limits
5 requests/second per API key. Add delay nodes when fanning out to many rows. See Rate limits.Next step
- Clay integration
- Huntr MCP — for agent-native workflows instead
- API Reference