Blastable API
✓ Official Vendor SpecMarketingEmail MarketingapiKey40 EndpointsREST
For Agents
Manage email lists, subscribers, templates, segments, senders, and campaigns in Blastable. Useful for agents that automate email marketing operations.
Use for: Add a new subscriber to a Blastable list, Bulk import subscribers into Blastable from a CSV, Unsubscribe an email address from every Blastable list, Look up a subscriber by email across all lists
Not supported: Does not handle SMS, push notifications, or transactional billing — use for email marketing list, subscriber, template, segment, sender, and campaign management only.
The Blastable API is the programmatic surface of Blastable, an email marketing platform focused on inbox deliverability. It exposes the full set of email-marketing primitives: lists, subscribers (including bulk create and cross-list search), templates, segments, senders, sending domains, and campaigns. Marketers use it to keep subscriber lists in sync with their CRM, manage transactional and broadcast templates, and orchestrate campaigns programmatically without the Blastable web UI.
Install Jentic One Beta
Connect the Blastable API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blastable 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.
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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 Blastable API.
Create, list, and delete email marketing lists in Blastable
Add subscribers individually or in bulk and unsubscribe them across one or all lists
Look up a subscriber by email or by custom field across the account
Manage email templates and segments used by campaigns
Configure senders, including resending the confirmation email and updating sender details
Drive Blastable campaigns from external workflows without using the web UI
Use Cases
Patterns agents use Blastable API for, with concrete tasks.
★ CRM-to-Blastable Subscriber Sync
Keep Blastable subscriber lists in sync with the CRM as contacts are created, updated, or marked as opted out. POST /lists/{list_uid}/subscribers/bulk handles the initial import, PUT /lists/{list_uid}/subscribers/{subscriber_uid} handles updates, and PUT /lists/subscribers/unsubscribe-by-email-from-all-lists removes a contact from every list when they revoke consent. This keeps marketing reach aligned with the source of truth.
POST /lists/{list_uid}/subscribers/bulk with a batch of new contacts, then PUT /lists/{list_uid}/subscribers/{subscriber_uid} for each contact whose record changed since the last sync.
Cross-List Unsubscribe Compliance
When a contact requests removal under data protection rules, the workflow must remove them from every Blastable list, not just one. PUT /lists/subscribers/unsubscribe-by-email-from-all-lists handles that single-call cross-list unsubscribe and GET /lists/subscribers/search-by-email-in-all-lists confirms the change. The audit log records the email and timestamp for compliance evidence.
Call PUT /lists/subscribers/unsubscribe-by-email-from-all-lists for the supplied email, then GET /lists/subscribers/search-by-email-in-all-lists to confirm zero remaining subscriptions.
Template and Sender Configuration Audit
Periodically audit the templates and senders on the Blastable account to make sure brand and compliance details are current. GET /templates lists every template, GET /senders lists configured senders, and PATCH /senders/{sender_uid} updates display names or footer details. POST /senders/{sender_uid}/resend-confirmation re-triggers verification when DNS or address changes.
Call GET /senders, flag any sender whose status is not verified, and call POST /senders/{sender_uid}/resend-confirmation to re-trigger verification.
Segment-Targeted Campaign Reporting
Pull the subscribers in a Blastable segment to size or QA a planned campaign before it sends. GET /segments lists segments, GET /segments/{segment_uid}/subscribers enumerates the audience, and the result feeds an internal QA step that confirms the audience size meets the campaign brief. The flow runs entirely server-side without exporting CSVs.
Call GET /segments, then GET /segments/{segment_uid}/subscribers for the chosen segment, and report the audience size to the campaign QA channel.
Agent-Driven Subscriber Add via Jentic
An AI agent capturing leads from a chat interface adds each new lead to the right Blastable list. It searches Jentic for 'add a new subscriber to a Blastable list', loads the POST /lists/{list_uid}/subscribers schema, and executes the call with the list id and subscriber email. The Blastable API key never leaves Jentic's vault, which is critical because the same key controls subscriber writes across the account.
Use Jentic search for 'add a new subscriber to a Blastable list', load the schema, then execute POST /lists/{list_uid}/subscribers with the email and required fields.
Key Endpoints
40 endpoints — the blastable api is the programmatic surface of blastable, an email marketing platform focused on inbox deliverability.
METHOD
PATH
DESCRIPTION
GET
/lists
List email lists
POST
/lists/{list_uid}/subscribers
Create a subscriber on a list
POST
/lists/{list_uid}/subscribers/bulk
Bulk create subscribers
PUT
/lists/subscribers/unsubscribe-by-email-from-all-lists
Unsubscribe an email from every list
GET
/lists/subscribers/search-by-email-in-all-lists
Find a subscriber by email across all lists
GET
/templates
List email templates
GET
/segments/{segment_uid}/subscribers
List subscribers in a segment
GET
/senders
List configured senders
GET
/lists
List email lists
POST
/lists/{list_uid}/subscribers
Create a subscriber on a list
POST
/lists/{list_uid}/subscribers/bulk
Bulk create subscribers
PUT
/lists/subscribers/unsubscribe-by-email-from-all-lists
Unsubscribe an email from every list
GET
/lists/subscribers/search-by-email-in-all-lists
Find a subscriber by email across all lists
GET
/templates
List email templates
GET
/segments/{segment_uid}/subscribers
List subscribers in a segment
GET
/senders
List configured senders
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Blastable uses an X-API-KEY header. Jentic stores the key in the encrypted vault and exposes only a scoped Jentic token to the agent — important because Blastable does not offer per-list scoping, so the raw key would otherwise expose the entire subscriber base.
Intent-based discovery
Agents search Jentic with intents like 'add a new subscriber to a Blastable list' or 'unsubscribe an email from every Blastable list' and Jentic returns the matching operation from the 40-endpoint spec with its input schema.
Time to first call
Direct integration: 1-2 days to wire the X-API-KEY header, list/subscriber CRUD, and bulk import error handling. Through Jentic: under 2 hours — search the operation, load schema, execute against /lists or /subscribers.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Blastable API through Jentic.
What authentication does the Blastable API use?
API key authentication via the X-API-KEY header (security scheme apiKey). Through Jentic the key is stored in the encrypted vault and the agent receives a scoped Jentic token instead of the raw key — important because the same key authorises subscriber writes across every list on the account.
Can I bulk import subscribers with the Blastable API?
Yes. POST /lists/{list_uid}/subscribers/bulk accepts a batch of subscriber records for the specified list, which is the right entry point for CRM exports or one-off imports. Use POST /lists/{list_uid}/subscribers for single inserts.
How do I unsubscribe an email from every Blastable list at once?
Call PUT /lists/subscribers/unsubscribe-by-email-from-all-lists with the email. This single call removes the contact from every list on the account, which is the pattern needed for compliance with data-protection unsubscribe requests.
What are the rate limits for the Blastable API?
The OpenAPI spec does not declare an explicit rate limit. Treat the API as paced for marketing operations rather than high-fan-out reads, and back off on HTTP 429 responses if a bulk import or audit script triggers throttling.
How do I add a Blastable subscriber through Jentic?
Install with pip install jentic, then use Jentic search with 'add a new subscriber to a Blastable list'. Jentic loads the POST /lists/{list_uid}/subscribers schema and executes it with the list id and subscriber details. The X-API-KEY header value never enters the agent's prompt.
Can I look up a subscriber by email across all lists?
Yes. GET /lists/subscribers/search-by-email-in-all-lists performs the cross-list search and returns each list the email is subscribed to. This is the right call for compliance lookups, customer-support investigations, or pre-import dedupe.
GET STARTED