Profiling Zendesk — 145 APIs and the Support Operating System

Zendesk has the largest non-cloud-infrastructure surface in the catalog — 145 distinct APIs. That number is startling for a product most people think of as “the help-desk ticket tool.” Walk the surface and the count makes sense: Zendesk isn’t a ticket form, it’s an operating system for customer support, and an OS has a lot of system calls.

What’s actually in the surface

The 145 APIs decompose into recognizable subsystems:

The ticket lifecycle — Tickets, Requests, Problems, Suspended Tickets, Deleted Tickets, Custom Status, Job Statuses. The core object, with every state of its life as its own surface.
Automation — Automations, Macros, Triggers (via targets), SLAs, Group SLAs, Approval Workflow Instances. The rules engine that runs support without a human in the loop.
Routing — Routing, Queues, Skips, Assignables, Group Memberships. Who gets which ticket.
Identity and org model — Users, Organizations, Groups, Custom Roles, Organization Memberships, Organization Merges.
Data modeling — Custom Objects, Object Layouts, Organization Fields, Relationships, Custom Statuses. Zendesk lets you extend its schema, and each extension point is an API.
Compliance and governance — Audit Logs, Chat Redactions, Comment Redactions, Chat File Redactions, Deletion Schedules, Deleted Users. PII handling as first-class surfaces.
Sync and search — Incremental, Imports, Search, Autocomplete, Dynamic Content, Locales.

What’s interesting about the shape

Redaction is its own API family. Three separate redaction surfaces (chat, comment, file) plus deletion schedules. When privacy regulation made “delete this customer’s data” a legal requirement, Zendesk turned it into a callable contract rather than a support request.
The schema is extensible through APIs. Custom Objects and Object Layouts mean Zendesk isn’t a fixed data model — it’s a platform you reshape via API. That’s why the count runs to 145.
Incremental sync is first-class. A dedicated Incremental API exists so downstream systems can mirror state efficiently. Most platforms bolt this on; Zendesk treats it as core.

The takeaway

One hundred forty-five APIs is what it looks like when a SaaS product becomes the system of record for an entire business function. The lesson isn’t “ship more APIs” — it’s that governance, extensibility, and sync each deserve their own surface once a product is load-bearing. Walk it on the Zendesk provider page.