beehiiv API

Name: beehiiv API
Brand: beehiiv API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail Marketingbearer67 EndpointsREST

For Agents

Manage newsletter subscriptions, publish posts, run automations, segment audiences, and operate paid tiers and referral programmes through beehiiv's 67 publication-scoped endpoints.

Install Jentic One Beta

Connect the beehiiv API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the beehiiv API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with beehiiv API.

Add, update, and tag newsletter subscriptions for a publication

Run bulk subscription imports and read job status from the bulk-update endpoints

Publish, schedule, and manage posts on a publication

Build and apply audience segments using condition sets and custom fields

GET STARTED

Start building with beehiiv API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use beehiiv API for, with concrete tasks.

★ Subscriber acquisition and CRM sync

Newsletter operators sync subscribers into beehiiv from website forms, lead magnets, and CRM exports so the audience of record stays in beehiiv. POST /publications/{publicationId}/subscriptions adds individuals, POST /publications/{publicationId}/bulk_subscriptions handles list imports, and the bulk_subscription_updates endpoints expose job status so the integration knows when an import has completed.

Add subscriber jane@example.com to publication pub_123 with custom field source set to landing_page_a and tag launch_2026

Audience segmentation for targeted sends

Operators segment their list using custom fields and behavioural signals so each post is sent to the readers most likely to engage. The /custom_fields and /condition_sets endpoints let an integration define attributes and rule sets, and /segments expose saved segments referenced when scheduling a post. This drives both engagement and reduced unsubscribe rates.

Create a custom field signup_source on publication pub_123 and build a segment of subscribers where signup_source equals podcast for a targeted promo send

Paid tiers and revenue reporting

Creators monetise through paid tiers on beehiiv and need revenue and tier-membership data for finance reporting. The /tiers endpoints expose tier configuration and per-subscription tier history, so an integration can build a monthly recurring revenue snapshot or detect downgrade and churn events for save-flow automations.

List all active paid subscriptions on publication pub_123, group by tier, and calculate the implied monthly recurring revenue

AI agent integration for creator operations

Independent creators and small newsletter teams use AI agents through Jentic to handle the long tail of operational tasks: tagging new subscribers, exporting weekly engagement reports, and setting up automation journeys for new signups. The agent searches Jentic for the right beehiiv operation, loads the schema, and executes with the bearer API key held in the Jentic vault, so the key never appears in agent context.

Through Jentic, find beehiiv's segments operation and produce a weekly report of subscriber growth, segmented by signup source, for publication pub_123

Key Endpoints

67 endpoints — jentic publishes the only available openapi specification for beehiiv api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/publications/{publicationId}/subscriptions

Add a subscriber

GET

/publications/{publicationId}/subscriptions

List subscribers with filters

POST

/publications/{publicationId}/bulk_subscriptions

Bulk import subscribers

GET

/publications/{publicationId}/posts

List newsletter posts

POST

/publications/{publicationId}/custom_fields

Define a custom subscriber field

GET

/publications/{publicationId}/segments

List saved audience segments

GET

/publications/{publicationId}/tiers

List paid tiers

POST

/publications/{publicationId}/webhooks

POST

/publications/{publicationId}/subscriptions

Add a subscriber

GET

/publications/{publicationId}/subscriptions

List subscribers with filters

POST

/publications/{publicationId}/bulk_subscriptions

Bulk import subscribers

GET

/publications/{publicationId}/posts

List newsletter posts

POST

/publications/{publicationId}/custom_fields

Define a custom subscriber field

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The beehiiv bearer API key is stored encrypted in the Jentic vault. Jentic injects the Authorization header at execution time so the key never enters agent context, and a key rotation in beehiiv settings updates the vault entry centrally.

Intent-based discovery

Agents search Jentic by intent (e.g. add a newsletter subscriber or create an audience segment) and Jentic returns the matching beehiiv operation with its input schema, so the agent calls /publications/{publicationId}/subscriptions or /publications/{publicationId}/segments without browsing docs.

Time to first call

Direct beehiiv integration: 1-3 days to wire publication scoping, custom fields, and bulk-import job polling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using beehiiv API through Jentic.

Why is there no official OpenAPI spec for beehiiv API?

beehiiv does not publish a downloadable OpenAPI specification alongside its developer docs. Jentic generates and maintains this spec so that AI agents and developers can call beehiiv API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the beehiiv API use?

beehiiv uses HTTP bearer authentication. Generate an API key from your publication's API integrations settings and pass it as Authorization: Bearer <token>. Jentic stores the key in its vault and injects the header at execution time so it never enters agent context.

Can I bulk import subscribers with the beehiiv API?

Yes. POST /publications/{publicationId}/bulk_subscriptions accepts a list payload and returns a job ID. Read /publications/{publicationId}/bulk_subscription_updates and /publications/{publicationId}/bulk_subscription_updates/{id} to track progress until the job completes.

How do I segment my audience through Jentic?

Search Jentic for create a beehiiv audience segment to find the segments and condition_sets endpoints. Load the schema and execute with your custom_field IDs and condition rules. Segments referenced when scheduling a post will narrow the recipient list to the matching subscribers.

Does the beehiiv API expose paid tier and revenue data?

Yes. /publications/{publicationId}/tiers lists configured tiers, and the subscriptions endpoints include tier membership per subscriber. Combine these to compute MRR, churn, and tier-distribution snapshots without exporting CSVs.

Can I register webhooks for subscription events?

Yes. POST /publications/{publicationId}/webhooks registers a webhook URL and event filter. The supported events cover subscription lifecycle changes and post events; consult the response schema to choose the events your integration cares about.

What are the rate limits for the beehiiv API?

beehiiv enforces per-publication rate limits described in its developer docs rather than in the OpenAPI spec. If you receive HTTP 429 responses, back off and retry with exponential delay, and contact beehiiv support if a sustained sync needs higher headroom.

beehiiv API

Connect the beehiiv API to your agent

Capabilities

Start building with beehiiv API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs