canonical: https://jentic.com/apis/clickfunnels.com # ClickFunnels APIs ClickFunnels is a sales funnel and online business platform. Jentic publishes and maintains the OpenAPI specifications for both ClickFunnels products: the ClickFunnels 2.0 API, which spans 204 endpoints across contacts, courses, forms, funnels, products, orders, sales pipelines, shipping, and webhooks; and the ClickFunnels Classic (1.0) API, with 11 endpoints for contacts, funnels and steps, purchases, and webhook subscriptions. Both use Bearer token authentication, letting agents run funnel-led marketing and commerce operations across whichever platform a workspace is on. ## For AI agents 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. ## Scope Use for: Managing funnel-led marketing and commerce on ClickFunnels 2.0 and Classic: contacts, funnels, courses, products, orders, sales pipelines, purchases, and webhook subscriptions. Not supported: - DNS provisioning - email deliverability infrastructure - domain provisioning - cross-workspace tokens - payment processing - page builder editing ## APIs | API | Category | Endpoints | Description | | --- | --- | --- | --- | | ClickFunnels API | marketing | 204 | Manage ClickFunnels 2.0 contacts, courses, forms, funnels, products, orders, sales pipelines, and webhooks across 204 endpoints from a single Bearer-authenticated API. | | ClickFunnels Classic API | marketing | 11 | Sync contacts, list funnels and steps, retrieve purchases, and manage webhook subscriptions on a ClickFunnels Classic account. | ## Which API to use | Need | API | Why | | --- | --- | --- | | Manage courses, products, orders, and sales pipelines | main | ClickFunnels 2.0 exposes 204 endpoints covering course delivery, storefront commerce, and pipeline automation that the Classic API does not have. | | Sync contacts, funnels, purchases, and webhooks on a 1.0 account | clickfunnels-api | ClickFunnels Classic serves accounts still on the original 1.0 product with a focused 11-endpoint surface at api.clickfunnels.com. | | Subscribe to outgoing webhook events | main | Both APIs offer webhook subscriptions; use the 2.0 API when the workspace is on the newer myclickfunnels.com platform. | ## Cross-API use cases ### Migrate contacts from Classic to 2.0 Move a marketing operation from ClickFunnels Classic to ClickFunnels 2.0 by reading contacts and funnel data from the Classic account and recreating contacts and tags on the 2.0 workspace. This lets an agent bridge the two platform generations during a migration without manual re-entry. Example prompt: List contacts via GET /contacts on the Classic API, then create each one via POST /contacts and apply tags via POST `/contacts/{contact_id}/applied_tags` on the 2.0 API. ### Unified purchase and order reporting Build a single revenue view across both ClickFunnels generations by pulling purchase records from a Classic account and order and transaction data from a 2.0 workspace. An agent can reconcile funnel revenue regardless of which platform a given account runs on. Example prompt: Page through GET /purchases on the Classic API and GET /orders on the 2.0 API, then aggregate amounts by funnel for a combined report. ### Consolidated webhook automation Set up event-driven automations for accounts spread across both platforms by subscribing outgoing webhooks on Classic funnels and on 2.0 orders. An agent can register and maintain webhook targets on whichever product each account uses. Example prompt: POST to /webhooks on the Classic API and POST to `/webhooks/outgoing/endpoints` on the 2.0 API to register the same downstream handler for both accounts. ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related vendors - **Shopify** — E-commerce platform for teams where the storefront is the primary surface and funnels are secondary. - **HubSpot** — CRM and marketing automation for nurture, lead scoring, and reporting downstream of funnel capture. - **Stripe** — Payment processing for reconciling ClickFunnels purchase and order records against the underlying processor. - **Kajabi** — Online course and membership platform that overlaps with ClickFunnels 2.0 course delivery. ## FAQ ### 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. ### How do agents find the right operation across both APIs? An agent searches 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. The agent does not need to know in advance which of the two APIs exposes a given capability.