Myclickfunnels ClickFunnels Email Broadcast CRUD API
67
AI ReadinessAI-Aware (B+)67/100
Community OpenAPI document · agent-readyMarketingEmail Marketingbearer5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
List, create, read, update, and remove ClickFunnels V2 email broadcasts, scoped to a workspace, with progress and revenue attributes where enabled.
Use for: I need to create an email broadcast in a workspace, I want to list the broadcasts in my workspace, Get a specific broadcast by its id, Update the content of an email broadcast
Not supported: Does not manage funnels, contacts, or payments. Use for creating and managing ClickFunnels V2 email broadcasts only.
The ClickFunnels Email Broadcast API manages email broadcasts in ClickFunnels V2. It lists broadcasts within a workspace, creates a new broadcast, and reads, updates, or removes an individual broadcast by id. Collection operations are scoped to a workspace while individual broadcast operations use the broadcast id directly, and progress, performance, and revenue attributes are available where the account has the analytics feature enabled.
Install Jentic One Beta
Connect the ClickFunnels Email Broadcast CRUD API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClickFunnels Email Broadcast CRUD 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyclickfunnels.com%2Fmyclickfunnels" | sh2
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%2Fmyclickfunnels.com%2Fmyclickfunnels" | 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 ClickFunnels Email Broadcast CRUD API.
List email broadcasts within a workspace
Create a new email broadcast in a workspace
Read an individual broadcast by its id
Update the content and settings of a broadcast
Remove a broadcast by its id
Read progress, performance, and revenue attributes where the analytics feature is enabled
Use Cases
Patterns agents use ClickFunnels Email Broadcast CRUD API for, with concrete tasks.
★ AI agent broadcast management via Jentic
An AI agent connected through Jentic manages email broadcasts without reading the ClickFunnels reference docs. It searches by intent such as creating a broadcast, Jentic returns the matching operation with its input schema, and the agent lists the workspace's broadcasts and creates a new one. The developer's own Jentic One instance injects the bearer token at call time.
Call GET /workspaces/{workspace_id}/emails/broadcasts to list broadcasts, then POST /workspaces/{workspace_id}/emails/broadcasts to create one
Programmatic campaign scheduling
Marketing tools queue broadcasts from an external system. The API creates a broadcast in a workspace and reads it back by id, so an agent can schedule a send from a content pipeline and confirm it was created with the right settings.
Call POST /workspaces/{workspace_id}/emails/broadcasts to schedule a broadcast, then GET /emails/broadcasts/{broadcast_id} to confirm it
Broadcast edits and cleanup
Teams revise or cancel queued sends. The API updates a broadcast's content and settings by id and removes a broadcast, so an agent can correct a subject line before send time or delete a broadcast that is no longer needed.
Call PATCH /emails/broadcasts/{broadcast_id} to edit a broadcast, or DELETE /emails/broadcasts/{broadcast_id} to remove it
Performance and revenue reporting
Reporting tools pull results after a send. Where the analytics feature is enabled, individual broadcast reads expose progress, performance, and revenue attributes, so an agent can retrieve the outcome of a broadcast and attribute revenue to it.
Call GET /emails/broadcasts/{broadcast_id} and read the performance and revenue attributes where enabled
Key Endpoints
5 endpoints — the clickfunnels email broadcast api manages email broadcasts in clickfunnels v2.
METHOD
PATH
DESCRIPTION
GET
/workspaces/{workspace_id}/emails/broadcasts
List broadcasts in a workspace
POST
/workspaces/{workspace_id}/emails/broadcasts
Create a broadcast
GET
/emails/broadcasts/{broadcast_id}
Get a broadcast
PATCH
/emails/broadcasts/{broadcast_id}
Update a broadcast
DELETE
/emails/broadcasts/{broadcast_id}
Delete a broadcast
GET
/workspaces/{workspace_id}/emails/broadcasts
List broadcasts in a workspace
POST
/workspaces/{workspace_id}/emails/broadcasts
Create a broadcast
GET
/emails/broadcasts/{broadcast_id}
Get a broadcast
PATCH
/emails/broadcasts/{broadcast_id}
Update a broadcast
DELETE
/emails/broadcasts/{broadcast_id}
Delete a broadcast
Jentic AI Readiness Score
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.
C
ClickFunnels Email Broadcast CRUD API
- AI-Aware (B+)67/100
72
Foundational Compliance63
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience94
Agent Usability60
Security80
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
88%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
51%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
70%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
80
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
80%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ClickFunnels Email Broadcast API by hand means learning its bearer scheme, satisfying the email-sending-api feature gate, and tracking that collection calls are workspace-scoped while reads use the broadcast id. Through Jentic you install once, import ClickFunnels from the API Directory, store the token once, and your agent calls the broadcast operations.
Permission scoping
ClickFunnels puts the workspace id in the URL path (/workspaces/{workspace_id}/emails/broadcasts), so a rule can pin your agent to one workspace. You choose the operations it may call, so creating, updating, or deleting a broadcast stays out unless you add them, leaving the agent to list and read.
Credential isolation
Your ClickFunnels bearer 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 'create an email broadcast' or 'list broadcasts', and Jentic returns the matching ClickFunnels operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ClickFunnels Email Broadcast CRUD API through Jentic.
What authentication does the ClickFunnels Email Broadcast API use?
The ClickFunnels Email Broadcast API authenticates with an HTTP bearer token in the Authorization header, per its OpenAPI spec, and requires the email-sending-api feature gate for all endpoints. Through Jentic, your token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I create an email broadcast with the ClickFunnels Email Broadcast API?
Yes. The create operation adds a broadcast within a workspace, and you can read it back by its broadcast id to confirm the settings. Collection operations are scoped to the workspace while reads, updates, and deletes use the broadcast id directly.
What are the rate limits for the ClickFunnels Email Broadcast API?
The OpenAPI spec does not state numeric rate limits, and progress, performance, and revenue attributes require the analytics feature gate. Check the ClickFunnels developer documentation at https://developers.myclickfunnels.com for current limits.
How do I create a broadcast through Jentic?
Search Jentic by intent such as creating an email broadcast, and it returns the ClickFunnels broadcast-create operation with its input schema. Create the broadcast in your workspace and read it back by id, with your token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the ClickFunnels Email Broadcast API?
Yes. ClickFunnels puts the workspace id in the URL path, such as /workspaces/{workspace_id}/emails/broadcasts, so a rule can pin your agent to one workspace and allow only listing and reading broadcasts. The create, update, and delete operations stay out unless you add them, and every call is logged by your self-hosted instance.
Is there a ClickFunnels Email Broadcast API MCP server?
You do not need an MCP server to give your agent the ClickFunnels Email Broadcast API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the broadcast operations on demand without loading another server's tool definitions into its context.
GET STARTED