AnnouncementMore from November 2026

REST API V1 retires on December 31, 2026, and API V2 gets new endpoints

REST API V1 stops working after December 31, 2026. API V2 can now assign conversations, change their tag and unsubscribe contacts from emails.

In short

  • REST API V1 endpoints stop working after December 31, 2026
  • API V2 can assign a conversation to a teammate or a team
  • API V2 can change a conversation's tag and unsubscribe a contact from emails
  • Help Center links can opt out of the messenger with data-customerly-ignore

Customerly's REST API V1 retires on December 31, 2026. If your product or any integration still calls the V1 endpoints, those calls will stop working after that date. API V2 keeps growing in the meantime.

Migrate to API V2

Migrate to API V2 before December 31, 2026: everything you need is in the API V2 documentation.

  • Announced: November 10, 2026

New in API V2

  • Assign a conversation: to a teammate or to a team (November 10).
  • Change a conversation's tag (November 12).
  • Unsubscribe a contact from emails (November 12).

Links to your Help Center can now opt out of opening in the messenger: add the data-customerly-ignore attribute to the link (November 5).

Related updates

See the full changelog
Product recap

September 2026: a Spam folder, WhatsApp Business app coexistence and a faster app

Spam emails get their own folder, you can keep replying from the WhatsApp Business app on a connected number, and the web app starts faster.

  • Emails flagged as spam by email providers land in a separate Spam folder
  • Connect a number you already use in the WhatsApp Business app and keep using the app
  • We updated the web app and the messenger to make them faster
  • New onMessengerLoadFailed callback for developers
InboxWhatsApp & channelsPlatform & securityAPI & developers
Customerly Project Settings with Inbox → Spam open and the Enable Spam inbox toggle switched on
New feature

Connect Customerly to Claude with MCP, with permissions you choose

Add Customerly to Claude as a custom connector over MCP and choose, resource by resource, what Claude can read or change. API tokens get expiry dates too.

  • Connect Claude to your Customerly workspace at https://mcp.customerly.io/mcp
  • Choose No access, Read only or Full access for each part of Customerly
  • The connection runs as you, so Claude can never do more than your own user
  • API access tokens can now have an expiration date and their own permissions
API & developersPlatform & security
Customerly Authorize MCP screen listing Lists, Emails, Inbox, Inbox complete access, Flows, Insights, Help Center and Surveys, each with no access, read only and full access options
Product recap

May 2026: launch flows from conversations and review Aura's replies

Launch any flow from inside a conversation, rate and flag Aura's replies, tune how she answers, and route work through new public API endpoints for inboxes and segments.

  • Launch any flow from inside an open conversation and let Aura take over
  • AI Flow Builder generates multiple coordinated flows and adds an On-Demand trigger
  • Rate and flag Aura's replies, with ratings rolled up under Insights → AI Effectiveness
  • Choose whether Aura includes images, videos or help center links, and her reply length
  • Delete a conversation permanently across channels for sensitive data and GDPR
Flows & automationAura AI agentInboxReports & insightsAPI & developers
Inbox conversation where a teammate opens More options, picks Launch a Flow, selects a flow from the list, and Aura takes over the conversation once the flow launches

AI Support That Sets You Apart.
Start Leading Today.

AI Support Software