canonical: https://jentic.com/apis/breaker.email/breaker

# Breaker Email Breaker API

The Breaker API creates and schedules newsletter email campaigns, reads their reporting, builds subscriber segments, and works with contacts from your own code. It covers automations, per-campaign and per-contact engagement, link-level click tracking, and custom fields and tags. A key belongs to one newsletter, so no endpoint takes a newsletter id.

## For AI agents

Create and send email campaigns, build segments, manage contacts and tags, and read opens, clicks, and unsubscribes for one newsletter.

## Scope

Does not handle SMS, transactional email, or payment collection. Use for newsletter email campaigns, segments, and reporting only.

## Capabilities

- Create, schedule, and export the rendered HTML of email campaigns
- Read campaign reporting: opens, unsubscribes, and clicks per link
- Build dynamic and static segments and recalculate them on demand
- Tag contacts and attach custom fields to your newsletter audience
- Create and update multi-step automations and their email content
- Track per-contact engagement and which contacts clicked a given link

## Use cases

### Agent-authored newsletter campaign

An AI agent that drafts newsletter content can create a draft campaign in Breaker, replace its body with the generated HTML, and schedule it, all against the single newsletter the key belongs to. The rendered email can be exported for a final human review before send.

Example prompt: Create a draft campaign titled 'October update', set its body content, and schedule it for the newsletter

### Engagement-based segmentation

A growth agent can build a dynamic segment whose rules target engaged readers, recalculate it, then list the contacts it contains, so a follow-up campaign reaches only people who opened or clicked recently. Breaker tracks per-contact engagement and clicks per link.

Example prompt: Create a dynamic segment of contacts who clicked any link in the last campaign and recalculate it

### Campaign reporting pull

A reporting agent can read a campaign's summary stats, its clicks per link, and the contacts who clicked a specific link, then read unsubscribes over a date range to produce a weekly performance digest for the newsletter owner.

Example prompt: Read the report for the latest campaign and list the contacts who clicked the top link

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/campaigns` | Create a draft campaign |
| PUT | `/campaigns/{campaignId}/content` | Replace a campaign body |
| GET | `/reports/campaigns/{campaignId}` | Stats for one campaign |
| GET | `/campaigns/{campaignId}/links` | Clicks per link for a campaign |
| POST | `/segments` | Create a segment |
| POST | `/contacts` | Create a contact |

## Key resources

- **Campaigns** — Create, schedule, read, and export newsletter email campaigns and their content
- **Automations** — Create and update multi-step automations and their email bodies
- **Reports** — Read campaign stats, clicks per link, subscriber count, and unsubscribes
- **Segments** — Create dynamic and static segments, edit their rules, and recalculate them
- **Contacts** — List and create contacts and attach tags and custom fields

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 73 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 77 / 100
  - AI-Readiness & Agent Experience: 58 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 78 / 100
- **View full report:** https://jentic.com/apis/breaker.email/breaker/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Breaker by hand means handling its bearer-token auth and remembering that each key is scoped to one newsletter, so no call takes a newsletter id. Through Jentic you install once, import Breaker from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** You choose which Breaker operations the agent may call, such as reading reports and building segments, so a destructive operation like deleting a draft campaign is not included unless you add it.
- **Credential handling:** Your Breaker key 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.
- **Discovery method:** Agents search Jentic by intent such as 'send a newsletter email campaign', and Jentic returns the matching Breaker operation with its input schema so the agent calls the right endpoint without browsing the docs.

## Related APIs

- **beehiiv** — beehiiv is a newsletter platform with growth tooling; Breaker exposes a focused campaign API.
- **Buttondown** — Buttondown is a lightweight newsletter tool; Breaker adds segments and automations.
- **Mailchimp** — Mailchimp is a broad email-marketing suite; Breaker keeps to newsletter campaigns.
- **Resend** — Resend sends transactional email; Breaker handles marketing newsletters.

## FAQ

### What authentication does the Breaker API use?

The Breaker API authenticates with an API key sent as a bearer token in the Authorization header, per its OpenAPI spec. A key belongs to one newsletter, so you create a separate key for each newsletter you work with.

### Is there a Breaker MCP server?

You do not need an MCP server to give your agent Breaker. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the campaign, segment, and reporting operations. No extra server tool definitions are loaded into the agent's context.

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

Yes. Write a rule that allows only the report-read and segment operations, so the agent can analyse engagement and build audiences but cannot delete or send a campaign, and every call it makes is logged.

### Can I read per-link click reporting with the Breaker API?

Yes. The campaign links endpoint returns clicks per link, and a further endpoint lists the contacts who clicked a specific link, so an agent can see exactly which readers engaged with which content.

### What are the rate limits for the Breaker API?

The OpenAPI spec does not publish a numeric rate limit. Check the Breaker documentation for the current limits before scheduling a large batch of campaigns or segment recalculations.

### How do I send a newsletter campaign with the Breaker API through Jentic?

Search Jentic for 'send a newsletter email campaign', and it returns the Breaker create-campaign operation with its input schema. Create the draft, set its content, and schedule it, all against the newsletter your key belongs to. To run it on your own infrastructure, install Jentic One from its GitHub repo.