FeedBlitz API

Name: FeedBlitz API API
Brand: FeedBlitz API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey7 EndpointsREST

For Agents

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

Connect the FeedBlitz API to your agent

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

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

GET STARTED

Start building with FeedBlitz API API

Explore with Jentic

View OpenAPI Document

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

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.

Use Cases

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

★ 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.

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.

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.

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 the Jentic vault.

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

Key Endpoints

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

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

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

Why though Jentic?

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

Credential isolation

FeedBlitz API keys are stored encrypted in the Jentic vault. Jentic appends the key query parameter at execution time, so the raw value is never visible to the agent or in logged URLs.

Intent-based discovery

Agents search by intent (e.g. 'add a feedblitz subscriber') and Jentic returns the matching FeedBlitz endpoint with its input schema.

Time to first call

Direct FeedBlitz integration: half a day for the seven endpoints. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mailchimp

Mainstream email marketing platform with broader template and automation tooling

Choose Mailchimp when you need richer drag-and-drop campaign authoring or e-commerce integrations.

Alternative

Brevo

All-in-one email, SMS, and CRM marketing platform

Choose Brevo when you need SMS, transactional email, and CRM in one product instead of RSS-driven email.

Complementary

ConvertKit (Kit)

Creator-focused email tool that pairs with FeedBlitz for blog-driven sends

Use ConvertKit when targeting newsletter creators with deeper subscriber tagging than FeedBlitz offers.

FAQs

Specific to using FeedBlitz API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.