Create post with the beehiiv API

Creates a post from HTML and returns its id; only on the Pro and Enterprise plans. status draft, the default, only saves it; confirmed sends and publishes it right away or at scheduled_at. beehiiv builds the post in the background, so Get post can answer 202 for a moment.

Identifier
beehiiv_create_post

The request

POST https://connect.reportei.com/api/tools/beehiiv_create_post/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "publicationId": "<publicationId>",
    "title": "<title>",
    "body_content": "<body_content>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
publicationIdstringYesId of the publication, from List publications.
titlestringYesTitle of the post.
subtitlestringNoSubtitle of the post.
body_contentstringYesContent as raw HTML. beehiiv removes style and link tags, so style the elements with inline style attributes.
statusstringNodraft only saves the post. confirmed sends and publishes it right away, or at scheduled_at. The default is draft.Values: draft, confirmed
scheduled_atstringNoWhen to publish a confirmed post, for example 2026-11-05T12:00:00Z.
thumbnail_image_urlstringNoURL of the thumbnail image.
content_tagsarrayNoContent tags of the post.
recipientsobjectNoWho gets it on each channel, with tier_ids free, premium or all. Without recipients, only the free tier gets it, on web and email; leave a channel out to skip it.
email_settingsobjectNoEmail options: email_subject_line (the default is the title), email_preview_text, reply_to_address (a verified reply-to address of the publication) and whether the title, subtitle and byline show in the email.
web_settingsobjectNoWeb options: the slug of the post URL, hide_from_feed, and whether the title, subtitle and thumbnail show on the web.
seo_settingsobjectNoSearch and social metadata of the web version.
social_sharestringNoSocial share buttons of the post.Values: comments_and_likes_only, with_comments_and_likes, top, none
email_capture_type_overridestringNoHow the web version asks visitors for their email.Values: none, gated, popup
custom_link_tracking_enabledbooleanNotrue turns on custom link tracking.
utm_params_enabledbooleanNoWhether UTM parameters go on the links. Without it, the setting of the publication applies.
utm_sourcestringNoutm_source of the links.
utm_mediumstringNoutm_medium of the links.
utm_campaignstringNoutm_campaign of the links.

Supported connections

Your customer connects their beehiiv account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/beehiiv_create_post. It becomes your agent's tool definition with no conversion.

Other beehiiv tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.