Agent-ready OpenAPI document · curated by JenticMarketingMarketing Automationbearer204 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage ClickFunnels 2.0 contacts, courses, forms, funnels, products, orders, sales pipelines, and webhooks across 204 endpoints from a single Bearer-authenticated API.
Use for: I need to apply a customer tag to a ClickFunnels contact after a webinar attended event, Enrol a contact in a course and mark the first lesson complete, Create a new product variant with its own price, List all open opportunities in a sales pipeline stage
Not supported: Does not handle DNS, domain provisioning, or email deliverability infrastructure - use for ClickFunnels 2.0 contacts, courses, forms, products, orders, and pipelines only.
Jentic publishes the only available OpenAPI specification for ClickFunnels API, keeping it validated and agent-ready. ClickFunnels 2.0 is the rebuilt sales funnel and online business platform, and its REST API exposes 204 endpoints covering contacts, courses, forms, funnels, products, orders, sales pipelines, shipping, and webhooks. The base URL is per-workspace at {subdomain}.myclickfunnels.com/api/v2 and authentication uses a Bearer token. The spec covers the same surface that powers webhooks, native integrations, and Zapier, so anything you can build on those rails you can call directly here.
Install Jentic One Beta
Connect the ClickFunnels API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClickFunnels 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%2Fclickfunnels.com%2Fclickfunnels-api" | 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%2Fclickfunnels-api" | 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 API.
Manage contacts and apply or remove tags via /contacts/{id} and /contacts/{contact_id}/applied_tags
Build courses with sections, lessons, and lesson completions via /courses, /courses/sections, /courses/lessons, and /courses/lesson_completions endpoints
Compose forms with field sets, fields, options, submissions, and answers via /forms and /form_submissions endpoints
List and configure funnels and their tags via /funnels and /funnels/tags endpoints
Manage products, variants, prices, and collections via /products, /products/variants, /products/prices endpoints
Process orders, fulfillments, invoices, and transactions via /orders, /fulfillments, and /orders/transactions endpoints
Track sales opportunities through pipeline stages via /sales/pipelines, /sales/pipelines/stages, and /sales/opportunities endpoints
Use Cases
Patterns agents use ClickFunnels API for, with concrete tasks.
★ End-to-End Course Delivery
Build, publish, and operate online courses inside ClickFunnels 2.0 by composing sections and lessons, enrolling contacts, and tracking lesson completions. The /courses, /courses/sections, /courses/lessons, /courses/enrollments, and /courses/lesson_completions endpoints together cover authoring, enrolment, and progress tracking from a single API.
Create a course via POST /courses, add a section via /courses/{course_id}/sections, then enrol the contact via /courses/{course_id}/enrollments.
Storefront and Order Management
Run a full storefront on ClickFunnels 2.0 by managing products, variants, prices, and collections, then processing orders, transactions, fulfillments, and invoices once a sale completes. The product, order, and fulfillment endpoints together replace separate e-commerce tooling for funnel-led commerce.
Create a product variant via POST /products/{product_id}/variants with the price ID, then on a new order create a fulfillment via /orders/{order_id}/fulfillments.
Sales Pipeline Automation
Turn captured leads into revenue by progressing opportunities through sales pipeline stages, attaching notes, and triggering downstream automations on each transition. The /sales/pipelines, /sales/pipelines/stages, /sales/opportunities, and /sales/opportunities/notes endpoints support the full sales workflow inside ClickFunnels.
Move opportunity 1234 to a new stage by updating it via PATCH /sales/opportunities/{id} and post a note via /sales/opportunities/{opportunity_id}/notes.
Form Capture and Submission Processing
Compose lead-capture forms with field sets, fields, and options, and process submissions and answers with structured access to every response. The /forms, /forms/field_sets, /forms/fields, /forms/submissions, and /forms/submissions/answers endpoints give programmatic control over the same forms that power funnels.
Create a form field set via POST /forms/{form_id}/field_sets, add fields, and on submission read /forms/submissions/{submission_id}/answers to capture each response.
AI Agent Workflow Orchestration via Jentic
An AI agent that runs marketing operations can move opportunities, tag contacts, fulfil orders, or post webhooks across ClickFunnels 2.0 by searching Jentic for the matching operation. Jentic securely stores the workspace bearer token so the agent only ever holds scoped execution rights, not the raw credential.
Use the Jentic search query 'tag a clickfunnels contact' to find POST /contacts/{contact_id}/applied_tags and execute with the contact ID and tag ID.
Key Endpoints
204 endpoints — jentic publishes the only available openapi specification for clickfunnels api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/contacts/{contact_id}/applied_tags
Apply a tag to a contact
POST
/courses/{course_id}/enrollments
Enrol a contact in a course
POST
/forms/submissions/{submission_id}/answers
Capture answers to a form submission
POST
/products/{product_id}/variants
Create a product variant
POST
/orders/{order_id}/fulfillments
Create a fulfillment for an order
PATCH
/sales/opportunities/{id}
Update a sales opportunity
POST
/webhooks/outgoing/endpoints
Subscribe to outgoing webhook events
POST
/contacts/{contact_id}/applied_tags
Apply a tag to a contact
POST
/courses/{course_id}/enrollments
Enrol a contact in a course
POST
/forms/submissions/{submission_id}/answers
Capture answers to a form submission
POST
/products/{product_id}/variants
Create a product variant
POST
/orders/{order_id}/fulfillments
Create a fulfillment for an order
PATCH
/sales/opportunities/{id}
Update a sales opportunity
POST
/webhooks/outgoing/endpoints
Subscribe to outgoing webhook events
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 API
- Foundational (C)53/100
40
Foundational Compliance62
Developer Experience & Jentic Compatibility58
AI-Readiness & Agent Experience43
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
40
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D-Signals: 4
0%
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).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
23%
Example Density
How richly the API is illustrated with examples.
73%
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.
58
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
67%
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.
66%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
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).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
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 API by hand means managing a workspace bearer token, resolving your own {subdomain}.myclickfunnels.com host, and mapping the right call across contacts, courses, forms, products, orders, and pipelines. Through Jentic you install once, import the ClickFunnels API from the API Directory, store the token once, and your agent calls it.
Permission scoping
ClickFunnels 2.0 puts resource ids in the URL path (/contacts/{contact_id}/applied_tags, /courses/{course_id}/enrollments, /orders/{order_id}/fulfillments), so a rule can pin your agent to one course and its enrollments. You choose the operations it may call, so writes like creating order fulfillments are not included unless you add them.
Credential isolation
Your ClickFunnels 2.0 workspace 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 'apply a tag to a contact' or 'enrol a contact in a course', 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 API through Jentic.
Why is there no official OpenAPI spec for ClickFunnels API?
ClickFunnels does not publish an OpenAPI specification for the 2.0 platform. Jentic generates and maintains this spec so that AI agents and developers can call ClickFunnels API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the ClickFunnels API use?
The API uses a Bearer token in the Authorization header, scoped to a specific workspace at {subdomain}.myclickfunnels.com. Through Jentic the workspace bearer token is stored in the encrypted vault and the agent receives only a scoped execution context.
Can I enrol a contact in a course and track lesson completion?
Yes. POST to /courses/{course_id}/enrollments with the contact ID, then create a lesson completion via /courses/{course_id}/lesson_completions when the contact finishes a lesson.
Can I manage product variants and prices via the API?
Yes. /products/{product_id}/variants creates variants, /products/{product_id}/prices manages pricing, and /products/collections groups products into collections for storefront merchandising.
How do I tag a ClickFunnels contact through Jentic?
Search Jentic for 'tag a clickfunnels contact', load the schema for POST /contacts/{contact_id}/applied_tags, and execute with the contact and tag IDs. The Python SDK uses await client.search, await client.load, await client.execute.
What is the base URL pattern for ClickFunnels API requests?
Requests go to https://{subdomain}.myclickfunnels.com/api/v2 where {subdomain} is the workspace identifier. The bearer token is scoped to that workspace, so cross-workspace calls require separate credentials.
Can I limit what my agent is allowed to do with the ClickFunnels API?
Yes. Jentic One is self-hosted, so your own rules decide which ClickFunnels 2.0 operations and which workspace credentials the agent may use. Because ClickFunnels puts resource IDs in the URL path, such as /contacts/{contact_id}/applied_tags, /courses/{course_id}/enrollments, and /orders/{order_id}/fulfillments, you can pin the agent to a single course and its enrollments or a single contact. You choose the operations it may call, so write actions like creating order fulfillments are excluded unless you explicitly add them.
GET STARTED