🧪 We have added new filters for different Product resources and the FormSubmission resource:

• FormSubmission -> id, page_id, contact_id
• Products::Collection -> id, visible_in_store, archived
• Products::Price -> id, visible, archived, variant_id
• Products::Tag -> id
• Products::Variant -> id, visible, archived, fulfillment_required
• Product -> id, visible_in_store, visible_in_customer_center

👤 You can now see when a tag was applied to a contact directly in the contacts payload.

Listening to subscription.items.changed enables listening for any line items changes for your subscription orders.

• You can now set up Webhooks::Outgoing::Endpoint resources with scope to funnels and pages via the API.
• ClickFunnels users will be able to create rich text descriptions for their product variants and collections. The API also reflects this in the Products::Variant and Products::Collection resources (at this point, this is in BETA).
• Courses::Enrollment resources can now be filtered by contact_id.

• All related Form APIs' routes in the docs now fully correspond to the actual routes.
• Archiving a Product visible in the Store now has a more concise error message.

We have added a lightweight Theme API so that you can read and update ClickFunnels themes programmatically and list your current Styles.

ClickFunnels OAuth API platforms make use of it to programmatically change styles in users' accounts based on their preferences inside of the platform app.

Check out this new set of Sales::Opportunity webhooks to power your automations whenever something happens on the CRM board: here.

Previously, you could have received a 200 response with an empty body.

You can also read more about our philosophy on requests and responses here:

https://developers.myclickfunnels.com/docs/requests-and-responses

You can now set up funnel-based webhooks via Zapier and the admin UI:

Please refer to the ℹ️ tooltip to see how it works. If you have any feedback or issues, reach out to ClickFunnels support.

We have been working on amazing new API and webhooks features, so we made available a bunch of new APIs for you to use on the way. 👇

New APIs

• Store API - Create, update and delete your workspace store programmatically.
• Funnel API - Get your funnel data and update your funnels dynamically, such as changing a funnel's live mode or tags based on real-life events.
• Funnel::Tag API - Read, create, update and delete funnel tags.
• Page API - List and update your user-facing pages (support for live HTML editing coming soon 🔮).

These APIs are part of bigger features, so we actively enhance them based on user feedback. If you have anything, please don't hesitate to share your thoughts with the ClickFunnels support (ask to forward your request to the API team) or in our funnel devs discussion forum. 👋

➕ Multiple redirect URIs for your OAuth app

If you offer your platform application as an OAuth app, you might be interested in having multiple redirect URIs, e.g. for development and production. This is now enabled in the UI in your Developer Portal in the ClickFunnels app.

🧺 Filtering for CRM API

Sales::Opportunity List endpoint is now filterable by:

• id
• pipeline_id
• pipelines_stage_id
• primary_contact_id
• assignee_id

Sales::Pipeline is filterable by:

• id

Sales::Pipelines::Stage is filterable by:

• id

🧑‍🔧 Product API fixes and additions

Today's deployment fixes a bug where Product#image_ids would become emptied when an update request was issued without an image_ids array.

We also fixed an issue where a too-long seo_description or seo_title would result in a 500 server error instead of an unprocessable 422 status code.

We also added a platform application public ID to Product::Variants to distinguish them when they were created by an API or OAuth application:

{
# ...
"created_by_platform_application": { "public_id": "SOME_PUBLIC_ID" }  
}