Buttondown API

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

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey10 EndpointsREST

For Agents

Manage Buttondown newsletters with a tight subscriber and email surface. 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.

Add new subscribers to a Buttondown newsletter

Look up an individual subscriber by ID

Update subscriber metadata such as tags or status

Remove subscribers from the audience

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 minimalist newsletter platform popular with writers and indie publishers. This curated spec exposes the core subscriber and email lifecycle — list, create, retrieve, update, and delete — for lightweight integrations. The companion buttondown-api spec covers the full surface when more resources are required.

Use Cases

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

★ Subscriber Lifecycle Sync

Mirror subscriber state between Buttondown and an external source of truth — a CRM, a billing system, or a community platform. Operators run hourly or daily syncs to keep the audience aligned and clean. POST and PATCH on /subscribers handle creation and updates respectively.

For each user marked active in the CRM, POST to /subscribers if missing, PATCH if metadata changed, and DELETE if the user has churned

Newsletter Draft Pipeline

Build automated draft pipelines that compose newsletter content from blog posts, AI summaries, or analytics digests, then create the email in Buttondown for human review. Editors approve in the Buttondown UI before sending. Saves 20-30 minutes of manual drafting per issue.

Pull the top three articles by traffic from analytics, summarise them, and POST to /emails as a draft titled 'Weekly Digest'

Audience Cleanup

Remove inactive or hard-bounced subscribers in bulk to keep deliverability strong. The DELETE method on /subscribers/{id} supports targeted cleanups, and PATCH lets an agent flag subscribers without removing them. A typical cleanup run completes in seconds for a small list.

List subscribers, identify those with no opens in 90 days, and PATCH them to a 'lapsed' tag for a re-engagement send

AI Agent Newsletter Operations

Through Jentic, an AI agent can drive Buttondown newsletter operations using natural language intent. The agent searches for the right operation, loads the schema, and executes — no doc-scraping required. Useful for assistants that publish on a writer's behalf.

Search Jentic for 'add a buttondown subscriber', load the schema for POST /subscribers, and execute with email and metadata fields

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscribers

List subscribers

POST

/subscribers

Create a subscriber

GET

/subscribers/{id}

Retrieve a subscriber

PATCH

/subscribers/{id}

Update a subscriber

DELETE

/subscribers/{id}

Delete a subscriber

GET

/emails

List emails

POST

/emails

Create an email draft

GET

/subscribers

List subscribers

POST

/subscribers

Create a subscriber

GET

/subscribers/{id}

Retrieve a subscriber

PATCH

/subscribers/{id}

Update a subscriber

DELETE

/subscribers/{id}

Delete a subscriber

GET

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

Agents search by intent (e.g., 'add a buttondown subscriber') and Jentic returns the matching operation with its input schema.

Time to first call

Direct Buttondown integration: half a day for auth and lifecycle handling. Through Jentic: under 30 minutes for the first working call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Buttondown API (full)

Full 118-endpoint Buttondown surface

Use when you need automations, attachments, exports, or other resources beyond subscribers and emails

Alternative

ConvertKit (Kit)

Creator-focused email platform with automations

Choose ConvertKit when richer automation flows are required

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

Pair with Buttondown when wider campaign tooling is needed alongside the newsletter

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 update an existing subscriber with the Buttondown API?

Yes. PATCH /subscribers/{id} updates the subscriber identified by the path parameter. Use this to change tags, metadata, or status without removing and recreating the record.

What are the rate limits for the Buttondown API?

Buttondown does not publish hard rate limits in the spec. For batch jobs, watch for 429 responses and back off rather than continuing tight retry loops.

How do I create an email draft through Jentic?

Run pip install jentic, then search Jentic with the query 'create a buttondown email draft', load the schema for POST /emails, and execute with subject and body fields.

How does this spec differ from the buttondown-api spec?

Both target the same base URL and authentication scheme. This spec covers 10 endpoints around the subscriber and email lifecycle; the buttondown-api spec covers 118 endpoints including automations, exports, attachments, and newsletter metadata.