ClickFunnels Classic API

Name: ClickFunnels Classic API API
Brand: ClickFunnels Classic API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer11 EndpointsREST

For Agents

Sync contacts, list funnels and steps, retrieve purchases, and manage webhook subscriptions on a ClickFunnels Classic account.

Quickstart

Get started with ClickFunnels Classic API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a funnel contact"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ClickFunnels Classic API API.

Create and update contacts on a ClickFunnels Classic account via POST /contacts and PATCH /contacts/{id}

List funnels owned by the account and inspect each funnel's steps via /funnels and /funnels/{funnel_id}/steps

Retrieve purchase records to power downstream reporting via /purchases

Subscribe to outgoing webhooks for funnel events via POST /webhooks

GET STARTED

Start building with ClickFunnels Classic API API

Explore with Jentic

View OpenAPI Document

Use for: I need to push a new contact into ClickFunnels Classic from a webinar signup, List every funnel on the account and its step structure, Retrieve all purchases recorded in the last 30 days for revenue reporting, Subscribe a webhook so my CRM gets notified when a contact opts in

Not supported: Does not handle course delivery, product catalogue, or order fulfilment — use for ClickFunnels Classic contacts, funnels, purchases, and webhooks only.

Jentic publishes the only available OpenAPI document for ClickFunnels Classic API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ClickFunnels Classic API, keeping it validated and agent-ready. ClickFunnels Classic (1.0) is the original sales funnel platform, and the Classic public REST API exposes the core resources marketers need to integrate funnels with their stack: contacts, funnels and their steps, purchases, and outgoing webhooks. The 11 endpoints cover contact upsert, funnel discovery, purchase listing, and webhook subscription management with Bearer token authentication.

Use Cases

Patterns agents use ClickFunnels Classic API API for, with concrete tasks.

★ Contact Sync to External CRM

Mirror ClickFunnels Classic contacts into a downstream CRM by upserting on POST /contacts when a new opt-in arrives and patching on /contacts/{id} when profile data changes. Combined with webhook subscriptions, the API supports near-real-time replication without polling.

POST a new contact to /contacts when a webinar signup webhook fires, then store the returned contact ID against the lead record in the CRM.

Purchase Reporting and Reconciliation

Pull purchase data from /purchases to reconcile ClickFunnels revenue against payment processors and accounting systems. The endpoint returns purchase records the marketer can join to contacts and funnel steps for funnel-level revenue attribution.

Page through GET /purchases for the last 30 days and aggregate amount by funnel ID using the contact and funnel lookups.

Webhook-Driven Automations

Subscribe a webhook on /webhooks to receive funnel events as they happen, so downstream systems can fire welcome emails, post to Slack, or hand off to support automatically. /webhooks/{id} lets you update or remove the subscription as targets change.

POST to /webhooks with the target_url and event types, then verify the subscription via GET /webhooks/{id}.

AI Agent Funnel Operations via Jentic

An AI agent watching marketing performance can pull funnel and purchase data, push contacts in, or set up webhook automations by searching Jentic for the matching ClickFunnels Classic operation. Jentic vaults the bearer token so the agent never sees the raw credential.

Use the Jentic search query 'create a funnel contact' to find POST /contacts and execute with the captured lead details.

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for clickfunnels classic api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/contacts

Create or upsert a contact

GET

/contacts/{id}

Retrieve a contact by ID

GET

/funnels

List funnels on the account

GET

/funnels/{funnel_id}/steps

List steps inside a funnel

GET

/purchases

List purchase records

POST

/webhooks

Subscribe to an outgoing webhook

DELETE

/webhooks/{id}

Delete a webhook subscription

POST

/contacts

Create or upsert a contact

GET

/contacts/{id}

Retrieve a contact by ID

GET

/funnels

List funnels on the account

GET

/funnels/{funnel_id}/steps

List steps inside a funnel

GET

/purchases

List purchase records

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The ClickFunnels Classic Bearer token is stored encrypted in the Jentic vault. Agents receive scoped execution rights and never see the raw token.

Intent-based discovery

Agents search Jentic by intent such as 'create a funnel contact' or 'list funnel steps' and Jentic returns the matching ClickFunnels Classic operation with its schema.

Time to first call

Direct ClickFunnels Classic integration: a couple of days to wire up contacts, funnels, purchases, and webhooks. Through Jentic: under 1 hour per workflow.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ClickFunnels 2.0

Newer ClickFunnels platform with 200+ endpoints across courses, products, and orders

Choose ClickFunnels 2.0 when the workspace is on the new platform and the workflow needs courses, products, or full e-commerce coverage.

Alternative

HubSpot

Marketing automation and CRM platform

Choose HubSpot when funnel-style capture also needs nurture sequences, scoring, and full CRM views.

Complementary

Stripe

Payment processing for funnel checkouts

Pair Stripe when reconciling ClickFunnels purchase records back to the underlying payment processor for finance reporting.

FAQs

Specific to using ClickFunnels Classic API API through Jentic.

Why is there no official OpenAPI spec for ClickFunnels Classic API?

ClickFunnels does not publish an OpenAPI specification for the Classic 1.0 platform. Jentic generates and maintains this spec so that AI agents and developers can call ClickFunnels Classic API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ClickFunnels Classic API use?

The API uses a Bearer token authorisation header, with API key as a query-parameter alternative documented by ClickFunnels. Through Jentic the bearer token is stored in the encrypted vault and the agent receives a scoped execution context only.

Can I create a contact and subscribe to events at the same time?

Yes. POST /contacts to create the contact, then POST /webhooks with the relevant event types so downstream systems are notified when that contact triggers funnel actions.

How do I list every step in a funnel?

Call GET /funnels to list funnel IDs, then GET /funnels/{funnel_id}/steps for each one to retrieve its ordered step structure. This is the source for funnel topology in reporting.

How do I push a ClickFunnels contact through Jentic?

Search Jentic for 'create a funnel contact', load the schema for POST /contacts, and execute with the contact details. The Python SDK uses await client.search, await client.load, await client.execute.

Is this the same API as ClickFunnels 2.0?

No. This spec covers ClickFunnels Classic (1.0) at api.clickfunnels.com. ClickFunnels 2.0 is a separate product with its own API at the per-workspace myclickfunnels.com domain and a much larger surface.