# Kit setup for PopMCP

You paste one Kit V4 API key, minted under Settings, Developer in the V4 Keys section.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.kit.com/v4
- Credentials screen: https://app.kit.com/account_settings/developer_settings
- Provider docs: https://developers.kit.com/api-reference/authentication

## Before you begin

- A Kit account, formerly ConvertKit. V4 keys are not plan-restricted
- Access to the account's own settings. Keys are per-user, not per-team-member

## Get your credentials

### 1. Open your Developer settings

Click Settings at the bottom left of the vertical nav and open Developer. You can also go straight to app.kit.com/account_settings/developer_settings.

Screen: https://app.kit.com/account_settings/developer_settings

### 2. Add a new V4 key

In the V4 Keys section click Add a new key and name it `PopMCP`. Click Create.

Screen: https://app.kit.com/account_settings/developer_settings

### 3. Copy the key before you close the dialog

Click Copy in the confirmation dialog and paste the value somewhere safe, then click Done.

### 4. Paste the key into PopMCP

Drop the value into API key and click connect.

## Fields PopMCP asks for

- API key (apiKey) [required]: In Kit go to Settings → Advanced → (or app.kit.com/account_settings/developer_settings) and create a V4 API key. Paste it here. It's sent as the X-Kit-Api-Key header and stored encrypted; used server-side only.

## Verify

PopMCP marks Kit as Connected and the subscriber tools return your list. The first call it makes is GET https://api.kit.com/v4/account.

## Troubleshooting

### 401 Unauthorized on every call

Cause: A V3 API key or V3 API secret was pasted instead of a V4 key, or the V4 key was reset after you copied it.

Fix: Go back to Settings, Developer, look under V4 Keys rather than the V3 section, and add a new key.

### You closed the dialog without copying the key

Cause: Kit reveals the key once, at creation.

Fix: Edit the key and click Reset to issue a new value, then paste that into PopMCP. Resetting invalidates the old value immediately.

### 429 Too Many Requests

Cause: API-key auth is capped at 120 requests per rolling 60 seconds.

Fix: Space out bulk runs, or build a Kit OAuth app if you need the 600 per 60 seconds ceiling.

### 403 on bulk or purchase endpoints

Cause: Those routes require OAuth, not an API key.

Fix: Use the individual endpoints, or register a Kit app for OAuth access.

### You cannot find Settings in the nav

Cause: Kit's vertical navigation moved Settings and the account menu to the bottom left of the screen.

Fix: Look at the bottom left, or press the search field at the top of the nav and type Developer.

---

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