canonical: https://jentic.com/apis/feedblitz.com/feedblitz

# FeedBlitz API

Jentic publishes the only available OpenAPI specification for FeedBlitz API, keeping it validated and agent-ready. FeedBlitz is an email marketing and RSS automation platform that turns blog feeds into newsletter campaigns and manages subscriber lists, autoresponders, and triggered sends. The API exposes seven endpoints covering account information, subscriber lifecycle, feed listings, campaigns, and triggers so a publisher can integrate FeedBlitz into a CMS, CRM, or audience-management workflow.

## For AI agents

List subscribers, add and remove them, and inspect feeds, campaigns, and triggers in a FeedBlitz account.

## Scope

Does not handle template authoring, A/B testing, or deliverability analytics - use for FeedBlitz subscriber, feed, campaign, and trigger reads and writes only.

## Capabilities

- Read FeedBlitz account information for the authenticated user
- List active subscribers across configured lists
- Add subscribers from external sources via `/subscribers/add`
- Remove subscribers via `/subscribers/remove` for unsubscribe automation
- List feeds, campaigns, and triggers configured on the account

## Use cases

### CRM-Driven Subscriber Sync

Marketing teams keep FeedBlitz lists in sync with their CRM. When a contact is created in HubSpot or Salesforce, a backend calls POST `/subscribers/add` with the email and target list to enrol them in the right newsletter, and POST `/subscribers/remove` on opt-out. The API key is passed via the query parameter so a server-side job is enough - no front-end SDK required.

Example prompt: On a HubSpot contact-created event, call POST `/subscribers/add` with the email and FeedBlitz list ID.

### Newsletter Audience Reporting

Publishers running multiple newsletters need a unified view of their FeedBlitz audience. GET /subscribers, GET /feeds, and GET /campaigns supply the raw data for a weekly dashboard that shows list size, active campaigns, and feed health without manually exporting CSVs from the FeedBlitz UI.

Example prompt: Pull GET /feeds and GET /subscribers each Sunday and write the totals into the analytics warehouse.

### Trigger-Based Welcome Series

Publishers configure FeedBlitz triggers to fire welcome and re-engagement sequences. GET /triggers exposes the configured triggers so a workflow tool can verify that the welcome series is still wired up before launching a campaign that relies on it.

Example prompt: Call GET /triggers and confirm the welcome trigger is present before scheduling the next launch campaign.

### Agent-Driven List Hygiene

An AI agent monitoring help-desk and support queues can spot opt-out requests in plain English and use Jentic to call POST `/subscribers/remove` against FeedBlitz, closing the loop on unsubscribes that would otherwise sit in a ticket queue. The FeedBlitz API key stays in your Jentic One instance.

Example prompt: Use Jentic to search 'remove a feedblitz subscriber' and execute POST `/subscribers/remove` with the email parsed from the support ticket.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/subscribers/add` | Add a subscriber to a list |
| POST | `/subscribers/remove` | Remove a subscriber from a list |
| GET | `/subscribers` | List subscribers |
| GET | `/feeds` | List configured feeds |
| GET | `/campaigns` | List campaigns |
| GET | `/triggers` | List triggers |

## Key resources

- **Account** — Read FeedBlitz account information
- **Subscribers** — List, add, and remove subscribers across lists
- **Feeds** — List configured RSS feeds powering FeedBlitz lists
- **Campaigns** — List campaigns scheduled or sent on the account
- **Triggers** — List autoresponder and trigger configurations

## Why Jentic

- **Setup:** Wiring the FeedBlitz API by hand means appending the key as a query parameter on every call and keeping it out of your own request logs yourself. Through Jentic you install once, import FeedBlitz from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** FeedBlitz identifies the subscriber and list in the request body rather than the URL path, so limit the agent to the operations it needs, such as adding a subscriber or reading feeds. You choose which operations it may call, so a write like removing a subscriber is included only when you add it.
- **Credential handling:** Your FeedBlitz API key is stored once, encrypted, by your own Jentic One instance and appended to the request at execution time. It never enters the agent's prompt, logs, or logged URLs.
- **Discovery method:** Agents search Jentic by intent such as 'add a FeedBlitz subscriber', and Jentic returns the matching FeedBlitz endpoint with its input schema so the agent calls the right endpoint without browsing the docs.

## Related APIs

- **Mailchimp** — Mainstream email marketing platform with broader template and automation tooling
- **Brevo** — All-in-one email, SMS, and CRM marketing platform
- **ConvertKit (Kit)** — Creator-focused email tool that pairs with FeedBlitz for blog-driven sends

## FAQ

### Why is there no official OpenAPI spec for FeedBlitz API?

FeedBlitz documents its endpoints on the legacy API page but does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FeedBlitz 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 FeedBlitz API use?

FeedBlitz uses an API key passed as the 'key' query parameter on each request. Through Jentic the key is stored in the vault and Jentic appends it at call time so it is not exposed in agent prompts or logs.

### Can I add and remove subscribers programmatically?

Yes. POST `/subscribers/add` adds a subscriber to a FeedBlitz list and POST `/subscribers/remove` removes them, supporting standard CRM-to-newsletter automation.

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

FeedBlitz does not publish numeric rate limits in this spec; throughput is constrained per account plan. Apply exponential backoff on 429 responses and contact FeedBlitz support if bulk operations need higher throughput.

### How do I add a subscriber to FeedBlitz through Jentic?

Run pip install jentic, search 'add a feedblitz subscriber', load POST `/subscribers/add`, and execute it with the email and list ID to enrol the contact.

### Can I list scheduled campaigns?

Yes. GET /campaigns returns campaigns configured on the account, useful for confirming send schedules before launch.

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

Yes. Because you run Jentic One yourself, you decide exactly which FeedBlitz operations your agent may call, so you can grant read-only access to GET /subscribers, GET /feeds, GET /campaigns, and GET /triggers while withholding writes. Since FeedBlitz identifies the subscriber and list in the request body rather than the URL, a write such as POST `/subscribers/remove` is available only when you explicitly add it to the agent's allowed operations. Your FeedBlitz API key stays in your own instance and is appended at call time, so the agent never sees it and can only act within the operations you have permitted.