ClickFunnels APIs for AI Agents
www.clickfunnels.com·Developer portal → developers.myclickfunnels.com
MarketingMarketing AutomationJentic-Generated SpecsBearer tokenAgent Ready
For Agents
APIs2 in catalogue
Endpoints215 indexed
AuthBearer token — 1 credential for all 2 APIs
ProvenanceJentic-generated specs
An agent can manage contacts, funnels, courses, products, orders, sales pipelines, purchases, and webhook subscriptions across ClickFunnels 2.0 and ClickFunnels Classic. It can sync leads, progress opportunities, fulfil orders, pull revenue data, and wire up event-driven automations on whichever ClickFunnels platform the account runs.
ClickFunnels covers two distinct platform generations under one brand: the broad ClickFunnels 2.0 surface for courses, storefront commerce, and sales pipelines, and the leaner ClickFunnels Classic 1.0 surface focused on contacts, funnels, purchases, and webhooks. Neither product ships an official OpenAPI spec, so Jentic generates and validates both so agents can call either one through structured tooling.
ClickFunnels API Catalog
2 APIs across 1 product group. All share one credential.
Marketing2
ClickFunnels APIManage ClickFunnels 2.0 contacts, courses, forms, funnels, products, orders, sales pipelines, and webhooks across 204 endpoints from a single Bearer-authenticated API.~204 endpointsClickFunnels Classic APISync contacts, list funnels and steps, retrieve purchases, and manage webhook subscriptions on a ClickFunnels Classic account.~11 endpoints
Which ClickFunnels API should I use?
| I want to... | Use |
|---|---|
| Manage courses, products, orders, and sales pipelines | ClickFunnels API |
| Sync contacts, funnels, purchases, and webhooks on a 1.0 account | ClickFunnels Classic API |
| Subscribe to outgoing webhook events | ClickFunnels API |
Install Jentic One Beta
Connect the ClickFunnels APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClickFunnels APIs, 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%2Fclickfunnels.com" | 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%2Fclickfunnels.com" | 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.
Once connected, ask your agent something like: “manage clickfunnels contacts and funnels”.
What AI Agents Can Do with ClickFunnels
Each workflow spans multiple ClickFunnels APIs. Jentic routes each operation to the right API automatically.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring both ClickFunnels products by hand means managing two separate Bearer tokens against two different hosts and mapping each call across contacts, funnels, courses, products, orders, and webhooks. With Jentic you install Jentic One once, add either ClickFunnels API from the Jentic directory, store each token once, and your agent calls both.
Permission scoping
Both APIs put resource ids in the URL path, so a rule in your own Jentic One instance can pin an agent to one funnel, course, or workspace. You choose which operations it may call, so writes like creating order fulfillments or deleting webhooks are excluded unless you add them.
Credential isolation
Each ClickFunnels Bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. The tokens never enter the agent's prompt, logs, or context, and the 2.0 and Classic credentials stay isolated from each other.
Intent-based discovery
Agents search the Jentic directory by intent such as tagging a contact or listing funnel steps, and Jentic returns the matching ClickFunnels operation with its input schema, so the agent calls the right endpoint on the right product without browsing reference docs.
FAQs
Specific to using ClickFunnels APIs through Jentic.
What is the difference between the two ClickFunnels APIs?
ClickFunnels 2.0 is the rebuilt platform with 204 endpoints covering contacts, courses, forms, funnels, products, orders, sales pipelines, shipping, and webhooks at a per-workspace myclickfunnels.com host. ClickFunnels Classic is the original 1.0 product with 11 endpoints for contacts, funnels, purchases, and webhooks at api.clickfunnels.com. Choose the one that matches the platform your account runs on.
Can one credential access both ClickFunnels APIs?
No. Each API uses its own Bearer token scoped to a different host. The 2.0 token is tied to a specific workspace subdomain on myclickfunnels.com, while the Classic token is scoped to api.clickfunnels.com. An agent working across both needs each token stored separately.
Which API should an agent use for e-commerce and courses?
Use the ClickFunnels 2.0 API. It is the only one of the two that exposes products, variants, prices, collections, orders, fulfillments, courses, sections, lessons, and sales pipelines. The Classic API is limited to contacts, funnels, purchases, and webhooks.
Why does Jentic publish specs for both products?
ClickFunnels does not publish an official OpenAPI specification for either the 2.0 or the Classic platform. Jentic generates and maintains both specs, validates them against the live APIs, and keeps them agent-ready so an agent can call whichever product an account is on through structured tooling.
Can an agent migrate data between the two platforms?
Yes. Because both APIs expose contacts and funnel data, an agent can read records from a Classic account and recreate contacts and tags on a 2.0 workspace. This supports assisting a migration from the original product to the rebuilt one without manual re-entry.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.