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

# Myclickfunnels ClickFunnels Email Broadcast CRUD API

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.

## For AI agents

List, create, read, update, and remove ClickFunnels V2 email broadcasts, scoped to a workspace, with progress and revenue attributes where enabled.

## Scope

Does not manage funnels, contacts, or payments. Use for creating and managing ClickFunnels V2 email broadcasts only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Call GET `/emails/broadcasts/{broadcast_id}` and read the performance and revenue attributes where enabled

## Key endpoints

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

## Key resources

- **Broadcasts** — List and create broadcasts in a workspace and read, update, or remove one by id

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 72 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/myclickfunnels.com/myclickfunnels/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 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 handling:** 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.
- **Discovery method:** 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

- **Mailchimp Marketing API** — Mailchimp sends and tracks email campaigns broadly, where this API manages broadcasts inside ClickFunnels V2.
- **Campaign Monitor API** — Campaign Monitor is a standalone email marketing platform; this API is scoped to ClickFunnels broadcasts.
- **Twilio SendGrid Single Sends** — SendGrid Single Sends covers one-off marketing emails that can run beside ClickFunnels broadcasts.
- **ClickFunnels API** — The broader ClickFunnels API manages funnels and contacts that the email broadcasts are sent to.

## FAQ

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