Buttondown Email Buttondown API

Name: Buttondown API
Brand: Buttondown API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey118 Endpoints

Install Jentic One Beta

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.

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbuttondown.email%2Fbuttondown-buttondown-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbuttondown.email%2Fbuttondown-buttondown-api" | 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.

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

Explore with Jentic One

View OpenAPI Document

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.

Use for: I need to import a CSV of subscribers into Buttondown, Schedule a newsletter for delivery next Tuesday at 9am, Set up an automation that emails new subscribers a welcome message, Attach a PDF to an outgoing newsletter email

Not supported: Does not handle SMS, push notifications, or transactional email for product flows - use for newsletter operations, automations, and audience management only.

Use Cases

Patterns agents use Buttondown 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the full Buttondown surface by hand means learning its token scheme, mapping 118 endpoints across subscribers, automations, exports, and coupons, and writing your own backoff for the undocumented 429s. Through Jentic you install once, import the Buttondown API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Buttondown puts resource ids in the URL path (/automations/{id}, /emails/{id}), so you can pin your agent to specific records instead of the whole account. You choose the operations it may call, so destructive ones like deleting an automation or triggering a draft send are not included unless you add them.

Credential isolation

Your Buttondown token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a buttondown email' or 'export buttondown subscribers', and Jentic returns the matching operation with its input schema, which matters when the surface spans well over a hundred endpoints and the correct path is hard to find by hand.

FAQs

Specific to using Buttondown 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Buttondown API?

Yes. Because you run Jentic One yourself, you decide which of the 118 Buttondown operations your agent may call, so destructive ones like deleting an automation or triggering a draft send stay out of reach unless you explicitly add them. Buttondown puts resource ids in the URL path, such as /automations/{id} and /emails/{id}, so you can pin the agent to specific records rather than the whole account. Your token is stored once by your own instance and injected only at execution time, so the agent acts strictly within the operations and records you allow.

Buttondown Email Buttondown API

Connect the Buttondown API to your agent

Capabilities

Start building with Buttondown API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs