Guide to Customer Help Desk APIs

Editor's note: This is a series on API-based integrations. Check out Merge if you're looking to add 10+ help desk integrations with one ticketing API.

Help desk software is the primary tool that customer support teams use day-in and day-out. So it’s not surprising that held desk software is commonly integrated with other products and that most have fully-featured APIs to support these integrations. If you’re building help desk integrations, accessing tickets via API, or working with help desk APIs, this article is your guide to:

  • Top APIs - Which help desks are most popular
  • Key concepts - How help desks work and how they differ
  • Data schemas - How help desk APIs organize customer data
  • Use cases - Common ways help desk data is used in product integrations
  • Getting started - Approaching help desk integrations to your product

Note: We’ll focus on customer-facing help desk APIs here. If you’re looking for other ticketing APIs such as internal-facing IT service desk APIs or software project management APIs, check out those articles as well.

Related: 5 ticketing API examples

Top Help Desk APIs

Customer help desk software is a booming business, with hundreds of vendors. There are three major segments of the help desk market. 

The largest, enterprise-focused help desks are Salesforce Service Cloud, Microsoft Dynamics 365, and Oracle Service Cloud, each part of broader CRM platforms (see our Guide to CRM APIs). 

SMB-focused vendors such as Zendesk, Freshdesk, Hubspot, and Zoho act as standalone help desks with CRM offerings as part of their platforms as well. 

SMB-focused vendors that emphasize their bundled chat and conversation-based functionality include LiveChat, Intercom, Help Scout, Front, Kayako, Gorgias, Gladly, and Live Agent.

Source: Company websites

Related: Examples of lead APIs

Key Help Desk Concepts

Although help desk APIs have similar objects and semantics, there are a couple of concepts that vary across APIs and are worthwhile to pay special attention to.

Agents and contacts

There are two relevant sets of individuals associated with any ticket. Support team members responsible for handling a ticket are typically identified by an Agent, Admin, or User object. Customers requesting support are typically identified by a Contact object. Some systems, however, use one object for both concepts. For example, the Zendesk API has a User object with an Agent ‘role’ for support team members and an End User type for customers.

Ticket hierarchies

Some help desks, such as Salesforce Service Cloud, offer the ability to have a hierarchy of tickets (aka Cases) to better organize complex or long-running support incidents. In these situations a ticket will have a parent reference.

Help Desk API Data Schemas

At the center of customer help desk data is the concept of a Ticket (aka conversation or case) that represents a support request or interaction. Each ticket is related to a contact that generated the support request and has assignees that are the support agents responsible to resolve the issue. Tickets also have statuses that they progress through as they are resolved. Tickets also include fields relating to their tags and types.

Tickets may have Comments associated with them as the contact and assignees (or multiple members of the support team) communicate back and forth. Comments also contain a body of text or HTML. Tickets may also have Attachments as a separate object.

Customers being helped are represented as Contacts, which include their name, email, and phone number. The Contacts belong to Accounts (aka companies) that are useful for organizing B2B support relationships.

Agents within the support organization are Users with names, emails, and roles. Users belong to Teams, which map to the support team org structure.

Related: How companies support their APIs

Top Help Desk API by SaaS Vertical

Customer experience 

Customer experience (CX) management systems include functionality for surveys, feedback forms, product requests, and voice of the customer. CX systems integrate with help desks to create new tickets or cases if a customer has negative feedback and to enrich tickets with contextual customer feedback and sentiment.

Examples: Uservoice, Productboard, SurveyMonkey, Medallia, Qualtrics

Qualtrics integrates with Hubspot to update ticket and CRM records, including triggering a new ticket when feedback or a survey is submitted.

Customer success management

Customer success management systems provide a broad view of both customer health and support team efficiency. Customer success platforms integrate with help desks to display tickets in the context of customer health scores, track overall customer analytics, and to add feedback and ratings on customer success interactions. 

Examples: Klaus, Gainsight, ChurnZero, Totango, Catalyst, ClientSuccess, Vitally

Totango integrates with the Zendesk API to read tickets and display key support data for a better view of customer success interactions by account.

Communication and chatbots

Tracking customer communication is a core functionality of every help desk system. Help desks integrate with voice, video, and chat tools to kick off new tickets, update ticket status, append transcripts, queue support requests, escalate and route support requests, and exchange files.

Examples: Ada, Olark, Aircall, Talkdesk, Dialpad, Genesys, Zoom

Ada integrates with Zendesk live chat to manage queuing, escalation, agent routing, and transcription.

Time tracking and billing

Help desk agents are often required to track their time on tickets to measure overall efficiency, bill clients for support, or get paid as a contractor. Time tracking software syncs with help desk systems to record the time spent per ticket and match it back to the client, project, and agent involved.

Examples: Harvest, Quickbooks Time, Replicon, Toggl, Evenhour, Clockify

Quickbooks integrates with the Freshdesk API to track time spent per ticket and to enrich ticket details with contact info from QuickBooks.

Incident management

Some help desk tickets require immediate attention from engineering or operations teams via an incident management system. Help desk systems integrate with incident management tools to create tickets from an ongoing incident, create an incident from a new ticket, and to link the two for ongoing updates.

Examples: PagerDuty, xMatters, Opsgenie, Statuspage

PagerDuty integrates with the Zendesk API to link incidents to tickets and display incident details.


Customer relationship management (CRM) software keeps a comprehensive record of a customer account, including support cases and tickets. CRM and help desk systems are commonly integrated to trigger new issues in the help desk from customer interactions, to provide rich customer context within the help desk, and to create new tasks in the CRM based on ticket status. 

Examples: Salesforce, Hubspot, Zoho, Microsoft Dynamics 365

Intercom integrates with Salesforce to sync help desk tickets with CRM tasks, accounts, and contact information.

Knowledge management

Customer support agents need relevant information at their fingertips, often stored within knowledge management systems. These systems integrate with help desks to surface relevant knowledge base articles, playbooks, and common answers in the context of a given ticket.

Examples: Guru, Notion, Confluence

Guru integrates with Kustomer to provide knowledge base suggestions that are optimized for language in tickets or customer records.

Getting Started with Customer Help Desk APIs

In addition to understanding customer help desk API schemas, you’ll also want to keep in mind a few additional topics as you start building:

  • API format - REST, SOAP, etc.
  • Authentication
  • Pagination
  • Rate Limits 
  • Test Accounts

If you don’t want to manage differences between each help desk API, you can use a unified API. Merge unifies multiple customer help desk APIs into one, making it easy to integrate your app with every vendor that your customers use. The Unified Ticketing API is REST-based, with common authentication, pagination, and rate limiting. It also includes automated logging and issue detection to make integration maintenance painless.