Changelog
New endpoints, improvements and breaking changes to the WhatsApp Platform API — newest first.
This is the dated record: when something arrived. How each feature works today is documented under Product for the Bitrix24 app and under Guides and the API reference for the API, and the entries below link there.
Breaking changes to the API are always announced here before they ship. New
event types are announced here too, which is why unknown event values in a
webhook payload should be ignored rather than treated as errors.
19 October 2026
Campaign and ad set on conversations from ads; WASync WhatsApp as a Bitrix24 message provider: WhatsApp messages from CRM Marketing campaigns, the Send message rule and the message button of a record; flows respect “Each number creates its own lead”; the inbox no longer trips Bitrix24's request limit on busy mornings; robots survive a deactivated first user.
18 October 2026
A What's new list inside the app with an unread dot; Chat Flows: an option to start only for customers who never wrote to you, no second lead for a customer with an open lead or deal, flow-created records assigned by your new-chats rule, and “Find a step” plus highlighted lines in the editor.
16 October 2026
A Chat rules setting that decides who may change the CRM stage from the WASync Chat header: all operators, admins only, or read-only for everyone.
15 October 2026
Smart Processes: the WASync tab on item cards, conversations linked to items, robots and Chat Flows on a process's automation rules, and ad attribution on items.
14 October 2026
An HTTP request step in Chat Flows, performed by an isolated worker under a fixed policy, and a guide for bringing a number from another provider.
10 October 2026
Quick replies with “/”, filled in for the open customer with CRM variables, language versions and a greeting by the customer's local time; in-product help for getting started with them; and a fix for duplicate leads with “Each number creates its own lead”.
9 October 2026
A chat flow per Meta ad and several inbound flows per number, a “+” on connection lines in the flow editor, flows that ignore re-delivered messages, and a choice of who is rung first for incoming calls.
8 October 2026
Answer WhatsApp calls in Bitrix24's own call card with the conversation beside it, the team rung after 8 seconds and through Staff access, an option for one lead per WhatsApp number, and an employee filter that follows each person's visibility.
7 October 2026
Create or link a lead from WASync Chat, rotation within a group in the Chat Flows “Assign to” step, long messages split on the WhatsApp Business API, honest durations for calls you place, the team rung when the responsible is offline, and the customer's WhatsApp photo and name in Bitrix24.
6 October 2026
Required fields before a stage change in WASync Chat, templates that keep their header image, chat visibility after a record is closed, the first step of the Chat Flows editor redesign, and leads that always come with a contact.
30 September 2026
Message media in EU object storage behind short-lived signed links, deleted and edited WhatsApp messages applied on QR connections, voice notes through the Business API, and a real health check behind every deploy.
29 September 2026
One conversation per contact across several numbers, with a sending-number picker, and a fix for new users whose first two hours of messages showed as read.
25 September 2026
Chat visibility rules per employee, enforced on the server, and automatic lead creation with round-robin assignment for chats from new numbers.
24 September 2026
Insert CRM fields into chat-flow messages, attach the file stored on the deal or lead, contact and company fields in flows, and values written the way a person would.
21 September 2026
A conversation whose deal was deleted repairs its own CRM link instead of writing into nothing.
19 September 2026
Passkeys, two-step sign-in and a security page for the developer console.
18 September 2026
Late delivery failures reach the Open Channel, and ad attribution always reaches the deal.
17 September 2026
Call permission end to end, buttons and the call-permission card in the template builder, two new flow nodes.
15 September 2026
Delete a number and close a workspace from the developer console, and Click-to-WhatsApp attribution that survives a Bitrix rejection.
14 September 2026
Create and revoke API keys from inside Bitrix24, and a checkout that repairs a stale Stripe customer on its own.
8 September 2026
A precise error when WhatsApp cannot find the recipient, and purchased slots that apply themselves.
18 August 2026
Pairing codes — connect a number without scanning a QR.
17 August 2026
API keys as the default credential, IP allowlists, webhook self-service, Idempotency-Key, and the canonical host.
8 August 2026
Connection lifecycle events and GET /account slot quota.
25 July 2026
Read receipts, and messageId becomes WASync's stable id.
13 July 2026
Webhooks reference, llms-full.txt and a CORS-open spec.
2 July 2026
402 responses carry a payment link when the API add-on is inactive.
19 June 2026
WhatsApp Platform API launch.
Developer console sign-in
Password, email code or passkey to sign in; a mandatory second step for new accounts; devices, activity and how to get back in if you lose access.
19 October 2026
Campaign and ad set ids on conversations from ads (with a Meta Ads token); WASync is a Bitrix24 message provider — pick "WASync WhatsApp" in CRM Marketing campaigns, in the "Send message" rule and in the message button of a record, and the customer gets a WhatsApp message; flows respect "Each number creates its own lead"; the inbox no longer trips Bitrix24's request limit at the start of a busy day; robots keep working when the portal's first user was deactivated.