The REST API: what it covers

The HuntSales REST API lets your own code use the same People Search and credits as the app. Create an API key under Admin, then Developer, and send it as a Bearer token. The full reference, with request and response examples, is at /docs/api.

What it covers: searching people (up to 5 People Search credits per page of 50, at 0.1 per person shown, and a page fetched in the last 7 days is free), adding people from a search to your CRM with their work email looked up (2 credits per person added with an email, nothing without), checking on each email lookup, reading your credit balance, and creating, listing and deleting your webhook endpoints and reading their recent deliveries. Searching and adding need the Live Search permission, managing webhook endpoints needs Automations, and the credit balance is open to every member's key. A key can never do more than its owner's role allows. Webhooks are the one place a key differs from the app: in the app only a superadmin manages them, while over the API a member's key with Automations manages the endpoints its owner created (a superadmin's key manages them all).

What it does not cover: there are no REST endpoints for contacts, lists, pipeline stages or campaigns. Those are available over MCP, which is how an AI assistant or your own code reads and changes them (see "Connect your own AI (MCP keys)" and /docs/mcp). Zapier and Make connect through signed webhooks and the incoming-webhook trigger instead.