Pipedrive deprecates its Channels API effective February 1, 2026
Pipedrive announced on November 14, 2025 that it is deprecating the Channels API, used by its Omnichannel API beta, with endpoints accessible until February 1, 2026 and existing messages kept as notes.
Pipedrive published a breaking change notice on November 14, 2025 deprecating the Channels API. The endpoints stayed available until February 1, 2026. The Channels API was used by the Omnichannel API beta, which let integrations bring messaging conversations into Pipedrive. Pipedrive says existing messages remain available as notes. Pipedrive says the change lets it concentrate on developing the next generation of its CRM. Conversation history is not lost, according to the company, because existing messages become notes. The entry directs developers with questions to the Developer's Community.
The details
- Deprecated endpoints: POST /v1/channels, POST /v1/channels/messages/receive, DELETE /v1/channels/{id} and DELETE /v1/channels/{channel-id}/conversations/{conversation-id}.
- Endpoints remained accessible until February 1, 2026.
- Messages linked to deals or other entities are kept as notes.
- Omnichannel API beta users must transition to an alternative solution.
Context
Pipedrive later added WhatsApp messaging to its CRM, announced May 26, 2026, alongside Projects and automation monitoring. The company also released a ChatGPT app in December 2025 and a native MCP server in June 2026. Separately, Pipedrive appointed Regi Vengalil as chief financial officer on December 2, 2025 and later opened data centres in Sydney and Montreal in May 2026.
Not disclosed
- A recommended replacement for Omnichannel API beta integrations
- How many integrations used the Channels API
- Vendor
Pipedrive- Category
- CRM & Marketing Automation
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.




