# beehiiv setup for PopMCP

You paste one beehiiv workspace API key into PopMCP, then pick which publications to connect and the PopMCP workspace each one goes into.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.beehiiv.com/v2
- Credentials screen: https://app.beehiiv.com/
- Provider docs: https://developers.beehiiv.com/welcome/create-an-api-key

## Approval required before this works

No one reviews you and most of the API works on every plan, but beehiiv only lets publications on the Pro and Enterprise plans create posts through the API (the Send API). Drafting, scheduling and publishing newsletter posts from the AI needs one of those plans.

- Typical wait: None. The post endpoints answer as soon as the publication is on Pro or Enterprise.
- Cost: Pro and Enterprise are priced by subscriber count on beehiiv.com/pricing. beehiiv's current plans are Free, Lite, Pro and Enterprise; guides written before its 2026 rename call Pro "Max" and Lite "Scale".
- Blocked until approved: create_post, update_post and the post template tools. Subscribers, custom fields, tags, lists, segments, automations, post stats and every other read keep working on Free and Lite.
- Works meanwhile: Connect on any plan and use the subscriber, segment, automation and analytics tools straight away. Draft posts in the beehiiv editor until the publication moves to Pro.

## Before you begin

- The Owner or Admin role in your beehiiv workspace. Only they can create API keys.
- Any beehiiv plan for subscribers, segments, automations and stats. Creating or updating posts through the API needs the Pro or Enterprise plan (Pro was called Max before beehiiv renamed its plans).
- Time for a quick identity check: beehiiv may ask you to verify your identity with Stripe when you create the key.
- If the key should reach only some publications, know which ones. You restrict it while creating or editing the key.

## Get your credentials

### 1. Open the API page in Workspace Settings

Sign in at app.beehiiv.com, click Settings, then click API under the Workspace Settings section.

Screen: https://app.beehiiv.com/

### 2. Create the key and choose its publications

Click Create New API Key and name it, for example `PopMCP`. Leave publication access open so the key reaches every publication in the workspace, or restrict it to the publications PopMCP should see. Complete the Stripe identity check if beehiiv asks for it.

Screen: https://app.beehiiv.com/

### 3. Copy the key before leaving the page

Copy the key straight away. beehiiv makes it inaccessible once you leave the page, so a lost key means creating a new one.

Screen: https://app.beehiiv.com/

### 4. Paste the key into PopMCP and pick publications

In PopMCP, paste the key into API key and click Connect beehiiv. PopMCP lists every publication the key can reach. Tick the ones to connect, choose the PopMCP workspace for each, and click the Connect button under the list.

## Fields PopMCP asks for

- API key (apiKey) [required]: In beehiiv: Settings → Workspace Settings → API → Create New API Key (you need to be a workspace Owner or Admin). Copy it right away, beehiiv only shows it once. A key can reach every publication in the workspace, or only the ones you restrict it to. Stored encrypted and used server-side only.

## Verify

PopMCP shows each publication as its own Verified connection labelled `beehiiv · <publication name>`. Asking the AI for the publication's subscriber count and average open rate returns real numbers.

## Troubleshooting

### 401 `The api key is not valid` (code INVALID_API_KEY)

Cause: The key was copied incompletely, or it was deleted in beehiiv.

Fix: Create a new key under Settings, Workspace Settings, API, copy it before leaving the page, and reconnect.

### A publication is missing from PopMCP's picker

Cause: The key is restricted to other publications. A restricted key cannot see the rest at all.

Fix: Edit the key in beehiiv to include that publication, or create an unrestricted key, then open the picker again.

### This beehiiv API key can no longer reach the connected publication

Cause: The key's publication list changed, or the publication was removed, so beehiiv answers 403 or 404 for it.

Fix: Reconnect beehiiv with a key that includes the publication.

### Creating or updating a post fails while other tools work

Cause: beehiiv only allows post creation through the API on the Pro and Enterprise plans.

Fix: Upgrade the publication to Pro or Enterprise, or draft the post in the beehiiv editor.

### get_post returns 202 or nothing right after create_post

Cause: beehiiv creates posts asynchronously, so the post can take a few seconds to appear. 404 POST_CREATION_FAILED means it will never exist.

Fix: Wait a few seconds and read it again. On POST_CREATION_FAILED, check the content and create it again.

### Data deletion or export tools are refused

Cause: beehiiv support has to enable exports and data deletion for your account, and a publication-restricted key gets 403 on data deletion.

Fix: Ask beehiiv support to enable the feature, and use an unrestricted key for workspace-wide deletion requests.

### 429 Too Many Requests

Cause: The key went over its per-minute allowance, which depends on your plan (30 a minute on Free).

Fix: Wait for the 60-second window to reset and retry. Bulk subscriber work goes faster on a higher plan.

---

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