Buttondown API

Name: Buttondown API API
Brand: Buttondown API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey118 EndpointsREST

For Agents

Drive end-to-end Buttondown workflows: subscribers, emails, automations, attachments, forms, exports, and account configuration. Authenticate with a Token in the Authorization header.

Connect the Buttondown API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buttondown 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.

Install Jentic One Beta (Self-Hosted)

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

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 Buttondown API API.

Manage the full subscriber lifecycle including imports and exports

Draft, schedule, and send newsletter emails with attachments

Configure automations that trigger on subscriber events

Maintain advertising units and ad slot placements

GET STARTED

Start building with Buttondown API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Buttondown API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Buttondown API, keeping it validated and agent-ready. Buttondown is a newsletter platform built for writers and indie publishers. This is the full surface — 118 endpoints across subscribers, emails, automations, attachments, books, coupons, comments, exports, forms, images, newsletters, notes, prices, snippets, and more. Use this spec when an integration needs deep coverage across the platform.

Use Cases

Patterns agents use Buttondown API API for, with concrete tasks.

★ End-to-End Newsletter Operations

Run the full newsletter lifecycle through the API — imports, drafts, scheduled sends, attachments, and post-send analytics. Publishers with engineering capacity build their own admin tooling on top of this surface. Initial integration takes a few days; ongoing operations are automated.

Create a newsletter email with an attachment, schedule it for 9am tomorrow, and tag the subscribers who should receive it

Automation and Onboarding Flows

Configure Buttondown automations through the /automations endpoints to trigger emails based on subscriber events such as signup, tag changes, or paid upgrades. Indie creators use this to build welcome sequences and re-engagement flows without managing a separate marketing automation tool.

Create an automation that sends a welcome email when a subscriber is tagged 'paid', then verify it appears via GET on the automations collection

Audience Export and Migration

Use the /exports endpoint to generate snapshots of subscribers, emails, or full account data. Operators use exports for migration to another platform, GDPR data subject requests, or warehouse loading. Exports run asynchronously and can be polled for completion.

Trigger an export of all subscribers via /exports, poll until complete, and store the resulting file in object storage

Paid Newsletter Monetisation

Configure prices, coupons, and subscription tiers through the prices and coupons endpoints. Writers running paid newsletters use this to launch campaigns, issue discount codes, and adjust tier pricing without touching the UI. Useful for time-bound promotions.

Create a 20% off coupon valid for 7 days and apply it to the standard monthly price

AI Agent Newsletter Operations

Through Jentic, an AI agent can drive any of the 118 Buttondown endpoints by intent. With this many resources, intent-based discovery removes the burden of finding the correct path manually. Useful for assistants that publish, moderate comments, or handle imports on a writer's behalf.

Search Jentic for 'schedule a buttondown email', load the schema for POST /emails, and execute with the body, subject, and scheduled_at fields

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/accounts/me

Read the authenticated account profile

GET

/advertising_units

List advertising units

POST

/advertising_units

Create an advertising unit

GET

/api_requests

Audit recent API requests

GET

/attachments

List attachments

POST

/attachments

Upload an attachment

GET

/advertising_units/slots

List ad slots

GET

/accounts/me

Read the authenticated account profile

GET

/advertising_units

List advertising units

POST

/advertising_units

Create an advertising unit

GET

/api_requests

Audit recent API requests

GET

/attachments

List attachments

POST

Why though Jentic?

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

Credential isolation

Buttondown API tokens are stored encrypted in the Jentic vault. Agents receive a scoped token at execution time — raw keys never enter the agent's context window.

Intent-based discovery

With 118 endpoints, agents rely on Jentic's intent search to locate the correct path and method, then load the schema to execute.

Time to first call

Direct Buttondown integration: 1-3 days for auth, error handling, and resource mapping across the full surface. Through Jentic: under 1 hour for the first working call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Buttondown API (curated)

Lighter 10-endpoint slice focused on subscriber and email lifecycle

Use the curated spec when only basic subscriber and email operations are needed

Alternative

ConvertKit (Kit)

Creator-focused email platform with automations and tags

Choose ConvertKit for a more mature creator ecosystem; pick Buttondown for editorial-first newsletters

Alternative

Beehiiv

Newsletter platform with monetisation and referral features

Use Beehiiv when revenue and growth tooling matter more than minimalist editing

Complementary

MailerLite

Broader email marketing platform with campaigns and landing pages

Pair with Buttondown when wider campaign and landing-page tooling is needed

FAQs

Specific to using Buttondown API API through Jentic.

Why is there no official OpenAPI spec for Buttondown API?

Buttondown does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Buttondown 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 Buttondown API use?

Buttondown uses a token-based API key passed in the Authorization header in the format 'Token YOUR_API_KEY'. Through Jentic, the key is stored in the encrypted vault and never enters the agent's context.

Can I configure automations with the Buttondown API?

Yes. The Automations resource lets you create and manage triggered email sequences such as welcome flows or re-engagement series, driven by subscriber events like tag changes or signup.

What are the rate limits for the Buttondown API?

Buttondown does not publish hard rate limits in the spec. For high-volume operations such as bulk imports or exports, throttle requests and watch for 429 responses; back off rather than retry tight loops.

How do I export all subscribers through Jentic?

Run pip install jentic, then search Jentic with the query 'export buttondown subscribers', load the schema for the /exports endpoint, and execute with the subscribers resource type. Poll the returned export ID until status is complete.

How is this spec different from the smaller buttondown spec?

Both target the same base URL (https://api.buttondown.com/v1) and the same Authorization Token authentication. This spec covers 118 endpoints including automations, attachments, exports, forms, prices, and coupons; the smaller buttondown spec curates 10 endpoints around the subscriber and email lifecycle for lightweight integrations.