beehiiv is automatable through its API

beehiiv is automatable today through its API. The opened posts reference requires an Authorization Bearer token. The OAuth 2.0 guide documents the authorization-code flow on https://app.beehiiv.com/oauth/authorize and /oauth/token, then Bearer access tokens. Scopes include read and write for posts, subscriptions, segments, custom fields, automations, podcasts, tiers, and webhooks, with identify:read as the default. A linked create-an-API-key page returned 403, so this record does not add a second authentication method. Getting started also links an OpenAPI download. Webhooks are documented for paid plans on Lite and above, delivered through Svix, and can be created in the app or with POST /webhooks. The same page says the beehiiv team maintains a Zapier integration and a Make integration. Power Automate and n8n were not opened. beehiiv documents a hosted MCP at https://mcp.beehiiv.com/mcp. v1 is read-only: it can analyze account data and cannot publish, edit, or change settings. The page says v2, with read and write, is coming soon. Sign-in is beehiiv OAuth. Developer docs also point clients at a separate docs MCP at https://developers.beehiiv.com/_mcp/server. No beehiiv CLI was established. Computer-use viability is unassessed. The API scores 7 and the product MCP scores 5. The API is the best path because it can write, while the current MCP cannot.

Best path today: api · Overall automatability: 7/10