External Purchase Endpoints now support a suppress_order_system_emails flag. When enabled, ClickFunnels will skip sending order confirmation, cancellation, and churned emails for orders created through that endpoint — useful when your external payment platform (e.g. ClickBank or CopeCart) already handles transactional emails.

A new read-only singleton endpoint GET /api/v2/workspaces/:workspace_id/emails/setting returns the workspace's configured email settings. The response includes the system and marketing from/reply-to email addresses (or null if not set). This endpoint is currently in BETA, along with the other Email resource endpoints.

Visit tracking data is now available on Contacts, Orders, Invoices, and Opportunities API responses. Each visit includes UTM parameters, referrer information, device details, and more — helping you attribute conversions and understand how contacts discover your funnels.

Orders API responses now include the origination_channel_public_id field, providing the obfuscated public ID for the origination channel. This makes it easier to link orders to their source channels in your integrations.

Resolved a rare edge case where the Scheduled Events API could return an error when a scheduled event referenced a deleted event type. The event_type field now correctly returns null in these cases.

The External Orders API is now available to everyone. You can use these endpoints to programmatically manage orders from external payment platforms or your own purchase solutions.

API error responses now return more descriptive and actionable error messages for edge case 500 errors, making it easier to diagnose and resolve issues with your API requests.

CopeCart joins ClickBank as the second external purchases integration. CopeCart merchants can now connect their accounts to ClickFunnels, with support for trials, renewals, cancellations, refunds, chargebacks, and multi-product External Orders.

Resolved an issue where customers on certain billing plans could encounter an authorization error when accessing the Developer Portal, despite having API access enabled on their plan.

You can now create, read, update, and delete email broadcasts via the API. Full CRUD operations are available at /workspaces/:id/emails/broadcasts and /emails/broadcasts/:id. Currently available in private beta — reach out on the developer forum to request access detailing your use case.