Zendesk is discontinuing Incremental API access for third-party developers effective January 19, 2027, citing data security risks as AI-driven workflows scale across customer organisations. The restriction targets bulk and incremental data transfer endpoints, which present significant breach exposure if third-party credentials are compromised—allowing rapid exfiltration of large datasets. Internal integrations remain unaffected, but any third-party app currently relying on these endpoints must migrate to alternative non-incremental APIs before the enforcement date. The phased rollout begins December 2, 2026, with a pause over the holiday period, giving developers roughly two months to complete migration work.
The implications for CX teams are material but manageable for most use cases. Zendesk has provided direct API alternatives for the majority of affected endpoints—ticket data, user records, chat logs, and custom objects all have viable replacements—though two voice channel endpoints lack alternatives, potentially creating friction for teams heavily dependent on call history integrations. Account administrators can request 60-day extensions starting November 2026 for partners requiring additional migration time, which provides a safety valve for complex integrations. The real pressure falls on third-party vendors and custom integration builders: those operating niche tools reliant on bulk data transfers will face the most disruption, whilst established marketplace partners likely have the resources to adapt quickly.
For CX leaders, the critical question is whether your current third-party ecosystem relies on these incremental endpoints—particularly for analytics platforms, workforce management tools, or AI-powered automation that ingests historical ticket or user data at scale. Teams should audit their active integrations now and flag any vendors using affected endpoints to begin migration conversations immediately. Zendesk's framing around AI security is sound; the move reflects legitimate concerns about credential compromise in an environment where third-party apps increasingly handle sensitive customer interactions. However, the lack of alternatives for voice call history suggests this policy may evolve, and teams should monitor the community forum for updates on those specific endpoints.
Announced on Rollout starts Rollout ends September 22, 2026 December 2, 2026 January 19, 2027 Zendesk is announcing the end of availability of Incremental APIs for third-party developers. To protect sensitive customer data and strengthen ecosystem security as AI workflows scale, access to endpoints
Announced on Rollout starts Rollout ends September 22, 2026 December 2, 2026 January 19, 2027 Zendesk is announcing the end of availability of Incremental APIs for third-party developers. To protect sensitive customer data and strengthen ecosystem security as AI workflows scale, access to endpoints