# Hunter setup for PopMCP

One Hunter API key, generated on the API keys page of your Hunter dashboard, pasted into PopMCP's API key field.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.hunter.io/v2
- Credentials screen: https://hunter.io/api-keys
- Provider docs: https://hunter.io/api-documentation/v2

## Before you begin

- A Hunter account, including the Free plan with its smaller monthly request allowance
- Sign in as the account whose data PopMCP should see, because the connection is locked to that key's account
- Enough monthly search and verification credits on the plan for the tools you intend to run

## Get your credentials

### 1. Sign in to Hunter

Sign in at hunter.io with the account that owns the data you want PopMCP to reach.

Screen: https://hunter.io/users/sign_in

### 2. Open the API keys page

Open hunter.io/api-keys from the account menu. Existing keys are listed with their name, masked value and creation date.

Screen: https://hunter.io/api-keys

### 3. Generate a key named for PopMCP

Click Create a new API key, name it `PopMCP`, then click Create. Copy the value with the Copy button rather than by selecting the text.

Screen: https://hunter.io/api-keys

### 4. Paste the key into PopMCP

In PopMCP, open the Hunter connector and paste the value into API key. Click Connect.

## Fields PopMCP asks for

- API key (apiKey) [required]: Hunter dashboard (hunter.io) → sign in → account menu → API → copy your API key. Stored encrypted; used server-side only (sent as the api_key parameter). The connection is locked to this key's account.

## Verify

PopMCP marks the Hunter connector Connected and shows your Hunter account email and remaining monthly credits. A test Domain Search returns email results for the domain you try.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The key was mistyped, carries a trailing space, or was deleted from hunter.io/api-keys.

Fix: Re-copy the key from hunter.io/api-keys with the copy button rather than by selecting text, then re-save the PopMCP connection.

### Requests succeed but return no emails and no error

Cause: Your monthly credits are exhausted, or the domain has no public addresses in Hunter's index.

Fix: Check the remaining credits on your Hunter dashboard, then upgrade the plan or wait for the monthly reset.

### 429 Too Many Requests

Cause: You crossed a per-endpoint rate limit. Discover is the tightest at 5 requests per second.

Fix: Slow the calls down and retry. The limits are per second and per minute, so a short pause clears them.

### Data looks like a different company's

Cause: The key belongs to a different Hunter account, such as a personal one rather than the team workspace.

Fix: Sign out, sign in as the correct account, generate a fresh key there and reconnect.

### Deleting a key broke another tool

Cause: Hunter keys are account-wide and often shared across the browser extension, the Sheets add-on and other integrations.

Fix: Keep one named key per integration so you can delete the PopMCP key on its own.

---

Source: https://www.docs.popmcp.com/docs/integrations/hunterio/