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.
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. ๐
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:
ClickFunnels users can create V2 and V1 webhook endpoints in the UI, thus enabling the triggering of V2 and V1 webhook events from the app. We have now enabled the ability to differentiate between those versions when listing endpoints and events by checking for the new api_version property. Additionally, we have added the common updated_at property to endpoints (events don't have it since they are immutable after creation).
You can now update or create a [Sales::Pipeline](https://developers.myclickfunnels.com/reference/listsalespipelinesstages) programmatically.
You can also update, create and remove a [Sales::Pipelines::Stage](https://developers.myclickfunnels.com/reference/createsalespipelinesstages) via the API.
We've also added a total_value and weighted_value to the Sales::Pipelines::Stage API resource and total_value to the Sales::Pipeline API so you can have a better overview of your opportunities value.
๐ Enrolling in a course via the API now gives users access to all lessons and modules.
๐ ๏ธ New filters
Filter [Contacts::Tag](https://developers.myclickfunnels.com/reference/listcontactstags#:~:text=object-,Filtering,-Keep%20in%20mind) by id or name.
In addition to id and contact_id, you can now filter Order by order_type (subscription-order or one-time-order).
๐ Writable contact custom attributes
You can now create new contact custom attributes and update existing ones directly on the Contact resource. You can learn all about it in the Body Params schema of any of the modifying endpoints like Create Contact, Update Contact or Upsert Contact.
Don't feel like coding? Check out our Zapier integration, where you can now also create and update custom contact attributes:
Right along with great improvements and additions to the CRM app in the ClickFunnels UI, you can now fully manage opportunities programmatically via the ClickFunnels API. To get your automations started, we have released:
Product collections in ClickFunnels are containers for a curated list of products or an automatic list (i.e., containing all products of the workspace). You can now create, update, and retrieve those collections via the new endpoints.
GET https://workspace.myclickfunnels.com/api/v2/orders?order_type=one-time-order
So now, when setting up the Zap and receiving test data, it is now ensured that only one-time orders are shown, excluding subscription orders in all cases.
Enjoy and let us know if you have any ideas, questions or doubts in the discussion forum ๐