The List Orders and List Invoices endpoints now return results significantly faster, especially for workspaces with large order volumes.

The Contacts API now exposes email_suppression_reason, is_active, and an email_engagement object containing last_email_sent_at, last_email_opened_at, and last_email_clicked_at. Email engagement data is returned when you pass expand[]=email_engagement in your request. An is_active filter is also available on the contacts index endpoint.

In some cases involving specific Stripe invoice sync timing, the subscription.first_payment_received webhook event could fail to fire, which is now fixed.

Additionally, the V2 order API and webhook payloads now include a recurring_invoices_paid_count field, which lets you identify first-time vs. renewal payments without needing a separate webhook.

POST /api/v2/workspaces/:workspace_id/orders now inherits the workspace currency setting.

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.