Beehiiv Integration
Connect Articfly to your Beehiiv publication and push AI-generated articles as Beehiiv posts via the REST v2 API. Two-step connect: paste a Beehiiv API key, pick which publication to publish to. Default status is "draft" so you can review every post before it goes live to subscribers.
Prerequisites
- ›A Beehiiv Enterprise plan with API access enabled. Beehiiv's Posts API is gated behind the Enterprise tier and your account team must explicitly turn on API access. Launch tier and Scale tier subscribers get HTTP 403 on every publish attempt. Articfly surfaces a warning at connect time and the integration page itself displays a banner explaining the tier gate.
- ›A Beehiiv API key, generated in your Beehiiv workspace settings (instructions below).
- ›Active Articfly account, sign up at app.articfly.com.
Connecting Your Beehiiv Publication
Two steps. Generate an API key, pick a publication.
Generate a Beehiiv API key
Open your Beehiiv dashboard and head to Settings → Integrations → API. Click Create new API key, name it Articfly, and copy the generated key. Beehiiv only shows the secret once. If the API section is missing from your settings, your workspace does not have API access enabled. Contact your Beehiiv account manager to confirm Enterprise tier and request API activation.
Paste the key and pick a publication
In the Articfly dashboard, go to Integrations → Beehiiv. Paste the key and click Continue. Articfly verifies the key against the Beehiiv API and lists every publication the key can access. Pick the publication you want Articfly to publish to and click Connect Beehiiv. Every Articfly post from this account lands in that publication.
What the Integration Does
Draft by Default
Articfly creates Beehiiv posts with status: draft by default. You review the post in Beehiiv's editor and hit Publish when ready. This is intentional, accidental sends to your full subscriber list are expensive to recover from.
HTML Content Body
Beehiiv accepts HTML for the post body. Articfly sends the article body as HTML, Beehiiv renders headings, paragraphs, lists, blockquotes, and inline images in the publication template you have configured.
Title, Subtitle, Thumbnail
Article title becomes the Beehiiv post title. Article excerpt becomes the subtitle (the line shown under the title in the post header). Featured image is sent as thumbnail_image_url, which Beehiiv displays in the post header and the publication archive grid.
Slug Mapping
Articfly sends the article slug to Beehiiv at web_settings.slug (Beehiiv nests the slug there, not at the top level). Edit the slug on the Articfly article detail page before publishing.
Web URL Backfill
Beehiiv's create response only returns the new post ID. Articfly fires a follow-up GET to /publications/{id}/posts/{postId} so the live web_url shows up in your Articfly dashboard right after publish.
PATCH on Update
Beehiiv's update endpoint uses HTTP PATCH (not PUT). Articfly handles this. When you re-publish an article from Articfly, the existing Beehiiv post is patched in place. Delete is not supported by the Beehiiv API, see Troubleshooting below.
Rate Limit Handling
On HTTP 429, Articfly waits for the timestamp in Beehiiv's X-RateLimit-Reset header and retries once. Beehiiv does not send Retry-After, so the reset header is the only signal.
Encrypted Key Storage
Your Beehiiv API key is encrypted at rest using AES-256-GCM. Articfly only decrypts it server-side at the moment of publish.
Security Notes
- ›The Beehiiv API key gives full publication access, posts, subscribers, segments. Treat it like a password.
- ›All API calls use HTTPS to
api.beehiiv.com/v2. Articfly never logs the raw key. - ›To fully revoke access, delete the API key in Beehiiv's Settings → Integrations → API. Disconnecting in Articfly clears the local copy but does not invalidate the key on Beehiiv's side.
- ›Articfly paginates publication lists up to 20 pages of 50 items (1,000 publications max per key). If your API key has access to more than that, only the first 1,000 show up in the picker.
Troubleshooting
"Beehiiv API returned 403" on publish
Your Beehiiv plan does not include API access. The Posts API is gated to the Enterprise tier with API access explicitly enabled by your Beehiiv account team. Launch and Scale plans cannot publish via the API regardless of which features the dashboard exposes. Contact Beehiiv support to confirm your tier and request API activation. Articfly cannot work around this, the 403 comes from Beehiiv's side.
"Beehiiv API key invalid"
Two possible causes. First, the key was deleted from Beehiiv Settings → Integrations → API after you connected, regenerate a fresh key and reconnect. Second, you pasted a key from a different Beehiiv workspace, the API rejects keys that do not match the publication you picked. Make sure the key was generated in the same workspace that owns the publication.
Cannot delete a post from Articfly
The Beehiiv API does not expose a delete endpoint for posts. Articfly's delete action throws a clear error pointing you to the Beehiiv dashboard. Archive or remove the post directly in Beehiiv under the publication's posts list. Future republishes from Articfly will still patch the existing post if it has not been archived.
Thumbnail image is not showing up
Beehiiv accepts thumbnails at thumbnail_image_url (not thumbnail_url). Articfly uses the correct field, so if the thumbnail is missing the image URL itself is the problem. Check that the article's featured image is a publicly reachable HTTPS URL. Beehiiv does not host images, it links to whatever URL you send. Articfly's pipeline hosts images on its own CDN by default, so this usually only breaks if you pasted a private or hotlinked URL.