Zendesk

aid: zendesk
url: https://raw.githubusercontent.com/api-evangelist/zendesk/refs/heads/main/apis.yml
apis:
- aid: zendesk:assignables
  name: Zendesk Assignables API
  tags:
  - Assignables
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/introduction/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/introduction/
    type: Documentation
  - url: openapi/assignables-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Assignables API lets you find out who or what can be assigned to a piece of worktypically a
    ticketgiven your accounts permissions, groups, and routing rules. It returns the set of eligible assignees (such
    as agents or groups) for a particular context, so you can build assignee pickers in custom apps, validate that an
    assignment is allowed before updating a ticket, or automate routing workflows.
- aid: zendesk:target-type
  name: Zendesk Target Type API
  tags:
  - Target Types
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/targets/targets/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/targets/targets/
    type: Documentation
  - url: openapi/target-type-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Target Types API exposes a catalog of the legacy target integrations your Zendesk account supportssuch
    as email or HTTP/URL targetsthat triggers and automations can use to send notifications or payloads to external
    systems. Its primarily a discovery endpoint: it lets you list the available target types and see the fields each
    one requires, so you can correctly create target instances with the Targets API.
- aid: zendesk:account
  name: Zendesk Account API
  tags:
  - Accounts
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://api.getbase.com
  humanURL: https://developer.zendesk.com/api-reference/sales-crm/resources/account/
  properties:
  - url: https://developer.zendesk.com/api-reference/sales-crm/resources/account/
    type: Documentation
  - url: openapi/account-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Account API lets you programmatically work with account-level records and settings so you can keep
    Zendesk in sync with the rest of your stack. In Zendesk Sell, it exposes endpoints to list, retrieve, create,
    update, and delete account objects (the companies you do business with), manage custom fields and tags, and relate
    accounts to contacts and deals, with search, filtering, and pagination for efficient data access.
- aid: zendesk:accounts
  name: Zendesk Accounts API
  tags:
  - Accounts
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://api.getbase.com
  humanURL: https://developer.zendesk.com/api-reference/sales-crm/resources/account/
  properties:
  - url: https://developer.zendesk.com/api-reference/sales-crm/resources/account/
    type: Documentation
  - url: openapi/accounts-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Sell Accounts API lets you programmatically manage the company records (accounts) in your CRM. It
    provides REST endpoints to create, read, update, and delete accounts; search and filter them; and work with
    related data such as associated contacts, deals, activities, notes, tags, and custom fields.
- aid: zendesk:activities
  name: Zendesk Activities API
  tags:
  - Activities
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/activity_stream/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/activity_stream/
    type: Documentation
  - url: openapi/activities-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Sell Activities API lets you programmatically manage the work your sales team doessuch as calls,
    emails, meetings, and tasksby creating, reading, updating, and deleting activity records. Activities can be linked
    to leads, contacts, and deals, include details like due dates, reminders, outcomes, owners, and notes, and can be
    filtered and paginated by type, status, user, or timeframe.
- aid: zendesk:any-channel
  name: Zendesk Any Channel API
  tags:
  - Channels
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/channel_framework/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/channel_framework/
    type: Documentation
  - url: openapi/any-channel-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Any Channel API (also called the Channel Framework) lets developers turn virtually any external
    communication sourcemessaging apps, social networks, SMS gateways, custom apps, or other platformsinto a
    firstclass Zendesk channel.
- aid: zendesk:approval-workflow-instances
  name: Zendesk Approval Workflow Instances API
  tags:
  - Approvals
  - Instances
  - Workflows
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/introduction/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/introduction/
    type: Documentation
  - url: openapi/approval-workflow-instances-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Approval Workflow Instances API lets you programmatically start, track, and manage approvals that are
    built with Zendesks workflow tools. Using REST endpoints, you can create an instance of a predefined approval
    workflow, associate it with a record such as a ticket, pass input data, and then query the instance to monitor its
    current state and steps.
- aid: zendesk:attachments
  name: Zendesk Attachments API
  tags:
  - Attachments
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket-attachments/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket-attachments/
    type: Documentation
  - url: openapi/attachments-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Attachments API lets you handle files that users add to Zendesk, primarily for ticket comments (and,
    via related endpoints, other content like help center articles). You upload a file to Zendesk storage to get an
    upload token, then reference that token when creating or updating a ticket comment so the file becomes an
    attachment.
- aid: zendesk:audit-logs
  name: Zendesk Audit Logs API
  tags:
  - Audit Logs
  - Audits
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/
    type: Documentation
  - url: openapi/audit-logs-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Audit Logs API lets you programmatically retrieve a chronological record of important administrative
    and security-related events in your Zendesk accountsuch as configuration changes, user and role updates,
    authentications, and other actions that affect account settings.
- aid: zendesk:autocomplete
  name: Zendesk Autocomplete API
  tags:
  - Autocomplete
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/organizations/organizations/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/organizations/organizations/
    type: Documentation
  - url: openapi/autocomplete-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Autocomplete API provides fast, typeahead-style suggestions for common Zendesk resourcesmost notably
    users and organizationsso your app can quickly find matches as someone types. You send a partial query (like a
    name or email) and get back a small, relevance-ordered list of candidates, limited to fields you need (for
    example, id, name, email) and filtered by the requesters permissions.
- aid: zendesk:automations
  name: Zendesk Automations API
  tags:
  - Automations
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/business-rules/automations/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/business-rules/automations/
    type: Documentation
  - url: openapi/automations-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Automations API lets you programmatically manage time-based business rules that keep Support tickets
    moving without manual work. Automations evaluate ticket conditions on a regular schedule (typically hourly) using
    time metrics like hours since creation, last update, or status change, and then perform actions such as changing
    status or priority, reassigning, adding tags, or sending notifications.
- aid: zendesk:bookmarks
  name: Zendesk Bookmarks API
  tags:
  - Bookmarks
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/ticket-management/bookmarks/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/ticket-management/bookmarks/
    type: Documentation
  - url: openapi/bookmarks-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Bookmarks API lets you programmatically manage an agents personal starred items in Zendesk, providing
    endpoints to list, create, and delete bookmarks. A bookmark is a lightweight record that points to another Zendesk
    resource (for example, something an agent wants quick access to in the interface), and its scoped to the user who
    created it. With the API you can fetch all of a users bookmarks, add new ones to surface important work, and
    remove those that are no longer relevant.
- aid: zendesk:brand-agents
  name: Zendesk Brand Agents API
  tags:
  - Brand Agents
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/brand_agents/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/brand_agents/
    type: Documentation
  - url: openapi/brand-agents-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Brand Agents API lets you programmatically manage which agents have access to which brands in a
    multibrand Zendesk Support account. It provides endpoints to list the agents associated with a given brand and to
    add or remove agents from that brand, so you can automate onboarding/offboarding, sync brand access from external
    directories, and enforce leastprivilege access at scale.
- aid: zendesk:brands
  name: Zendesk Brands API
  tags:
  - Brands
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/brands/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/brands/
    type: Documentation
  - url: openapi/brands-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Brands API is part of the Zendesk Support API that lets you programmatically manage a multibrand
    setup. It provides endpoints to list, create, update, delete, and fetch the default brand, along with
    brand-specific settings used across the agent workspace, Help Center, and email.
- aid: zendesk:channels
  name: Zendesk Channels API
  tags:
  - Channels
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/channel_framework/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/channel_framework/
    type: Documentation
  - url: openapi/channels-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Channels API (Channel Framework) lets developers build custom integrations that bring messages from
    any external source into Zendesk and send agent replies back out to the original channel. With it, you can
    register and configure channel accounts, accept inbound messages and attachments, map senders to end users, create
    or update tickets/conversations, preserve threading and context with metadata, and use channelback to post agent
    replies to the thirdparty system.
- aid: zendesk:chat-file-redactions
  name: Zendesk Chat File Redactions API
  tags:
  - Chats
  - Fiiles
  - Redactions
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/live-chat/chat-api/chats/
  properties:
  - url: https://developer.zendesk.com/api-reference/live-chat/chat-api/chats/
    type: Documentation
  - url: openapi/chat-file-redactions-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Chat File Redactions API lets administrators and trusted tools permanently remove files that were
    shared in live chat conversations. By redacting a file, its asset is taken out of circulation so it can no longer
    be downloaded or accessed via its URL, helping teams remediate accidental sharing of sensitive information and
    meet privacy or compliance requirements (for example, GDPR or CCPA).
- aid: zendesk:chat-redactions
  name: Zendesk Chat Redactions API
  tags:
  - Chats
  - Redactions
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/live-chat/chat-api/chats/
  properties:
  - url: https://developer.zendesk.com/api-reference/live-chat/chat-api/chats/
    type: Documentation
  - url: openapi/chat-redactions-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Chat Redactions API lets you programmatically remove sensitive information from chat transcripts and
    any shared files, so teams can meet security and privacy requirements without deleting entire conversations. You
    can target specific parts of a message (for example, a credit card number or password), redact an entire message,
    or remove an attachment; the change is permanent and designed to preserve the rest of the transcript and its
    metadata.
- aid: zendesk:comment-redactions
  name: Zendesk Comment Redactions API
  tags:
  - Comments
  - Redactions
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/
    type: Documentation
  - url: openapi/comment-redactions-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Comment Redactions API lets you programmatically and permanently remove sensitive information from
    ticket conversations without deleting the entire message. By targeting a specific ticket comment and supplying the
    text to scrub (for example, credit card numbers, passwords, or PII), the API replaces the matching content in both
    the plain text and HTML versions with a redacted placeholder and records a redaction event in the tickets audit
    trail.
- aid: zendesk:custom-objects
  name: Zendesk Custom Objects API
  tags:
  - Custom Objects
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/custom-data/introduction/
  properties:
  - url: https://developer.zendesk.com/api-reference/custom-data/introduction/
    type: Documentation
  - url: openapi/custom-objects-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Custom Objects API lets you model and store your own business datasuch as orders, subscriptions,
    devices, or contractsdirectly in Zendesk and relate it to native resources like tickets, users, and organizations.
    With it, you define object types and fields, create, read, update, and delete records, and establish one-to-one or
    one-to-many relationships so agents and workflows can access rich context in the Agent Workspace.
- aid: zendesk:custom-roles
  name: Zendesk Custom Roles API
  tags:
  - Custom Roles
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/custom_roles/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/custom_roles/
    type: Documentation
  - url: openapi/custom-roles-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Custom Roles API lets you programmatically manage the agent permission sets used in Zendesk Support
    (typically on Enterprise plans). Through it, you can list and fetch existing roles, create new ones, update their
    names, descriptions, and granular permissions, and delete roles you no longer need.
- aid: zendesk:custom-status
  name: Zendesk Custom Status API
  tags:
  - Custom Status
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/custom_ticket_statuses/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/custom_ticket_statuses/
    type: Documentation
  - url: openapi/custom-status-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Custom Status API lets you programmatically manage the custom ticket statuses your account uses beyond
    the builtins. With it, you can list and retrieve statuses, create new ones, update labels and descriptions for
    agents and end users, localize translations, activate or deactivate statuses, and control their display order.
- aid: zendesk:custom-statuses
  name: Zendesk Custom Statuses API
  tags:
  - Custom Statuses
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/custom_ticket_statuses/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/custom_ticket_statuses/
    type: Documentation
  - url: openapi/custom-statuses-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Custom Statuses API lets you programmatically create, read, update, delete, and reorder the custom
    ticket statuses your account uses, giving you more granular workflow states while still rolling up to Zendesks
    core status categories (like New, Open, Pending, On-hold, Solved, Closed) for SLAs and reporting.
- aid: zendesk:deleted-tickets
  name: Zendesk Deleted Tickets API
  tags:
  - Deleted Tickets
  - Tickets
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/
    type: Documentation
  - url: openapi/deleted-tickets-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Deleted Tickets API lets you manage tickets that have been soft-deleted in Zendesk Support. It
    provides endpoints to list and inspect deleted tickets, restore them to an active state if they were removed by
    mistake, or permanently delete them when you need to purge data. The API also supports bulk restore and bulk
    permanent deletion for handling many tickets at once.
- aid: zendesk:deleted-users
  name: Zendesk Deleted Users API
  tags:
  - Deleted Users
  - Users
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/users/users/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/users/users/
    type: Documentation
  - url: openapi/deleted-users-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Deleted Users API lets administrators manage users who have been soft-deleted in a Zendesk Support
    account. It provides endpoints to list and inspect deleted user records, restore a deleted user to an active state
    if the deletion was accidental, or permanently purge a user when you need to remove their personal data for
    compliance.
- aid: zendesk:deletion-schedules
  name: Zendesk Deletion Schedules API
  tags:
  - Deletion Schedules
  - Schedules
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/business-rules/deletion_schedules/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/business-rules/deletion_schedules/
    type: Documentation
  - url: openapi/deletion-schedules-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Deletion Schedules API lets you programmatically plan and manage future-dated deletions of data in
    Zendesk to meet retention and privacy requirements (for example, GDPR/CCPA). Instead of deleting immediately, you
    create schedules that target specific records (such as user or ticket data), choose when the deletion should
    occur, and then monitor, update, or cancel those schedules before they run.
- aid: zendesk:dynamic-content
  name: Zendesk Dynamic Content API
  tags:
  - Content
  - Dynamic Content
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/ticket-management/dynamic_content/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/ticket-management/dynamic_content/
    type: Documentation
  - url: openapi/dynamic-content-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Dynamic Content API lets you manage reusable, localized text snippetscalled dynamic content itemsso
    you can keep messages consistent across macros, triggers, automations, email notifications, and apps. With it, you
    can programmatically create, read, update, and delete items; add and edit language variants; set a default locale;
    and activate or deactivate content.
- aid: zendesk:email-notifications
  name: Zendesk Email Notifications API
  tags:
  - Email
  - Notifications
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/email_notifications/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/email_notifications/
    type: Documentation
  - url: openapi/email-notifications-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Email Notifications API (in Zendesk Support) lets admins and developers programmatically inspect the
    outbound emails Zendesk sendssuch as ticket update notifications. It exposes searchable delivery logs and metadata
    for each message, including recipient, subject, timestamps, delivery status (for example delivered, deferred,
    bounced, or complaint) and failure reasons, plus identifiers that help trace which ticket or business rule
    triggered the email.
- aid: zendesk:group-memberships
  name: Zendesk Group Memberships API
  tags:
  - Groups
  - Memberships
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/groups/group_memberships/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/groups/group_memberships/
    type: Documentation
  - url: openapi/group-memberships-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Group Memberships API lets you programmatically manage the relationship between users (typically
    agents) and groups in a Zendesk Support account. With it, you can list memberships across the account or scoped to
    a specific user or group, add a user to a group, remove a user from a group, and set which group is an agents
    default. Each membership ties a user_id to a group_id and can indicate the default group that agent belongs to,
    which affects ticket routing and workflows.
- aid: zendesk:group-slas
  name: Zendesk Group SLAs API
  tags:
  - Groups
  - Service Level Agreements
  - SLA
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/business-rules/group_sla_policies/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/business-rules/group_sla_policies/
    type: Documentation
  - url: openapi/group-slas-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Group SLAs API lets you manage and report on service-level targets that are scoped to support groups,
    not just to tickets overall. With it, you can programmatically create and update SLA policies that define
    different reply and resolution time targets per group, determine which policy and targets are applied to a given
    ticket as it moves between groups, and retrieve timing details such as remaining time, breach status, and pauses.
- aid: zendesk:groups
  name: Zendesk Groups API
  tags:
  - Groups
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/groups/groups/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/groups/groups/
    type: Documentation
  - url: openapi/groups-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Groups API lets you programmatically manage the agent groups that power ticket routing and workflows
    in Zendesk Support. With it, you can create, list, retrieve, update, and delete groups, as well as fetch the set
    of groups a user can assign tickets to (assignable groups). Groups are used in ticket assignment, views, macros,
    and business rules like triggers and automations, so the API enables you to integrate group management into your
    provisioning and operations tooling.
- aid: zendesk:imports
  name: Zendesk Imports API
  tags:
  - Imports
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_import/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_import/
    type: Documentation
  - url: openapi/imports-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Imports API lets you programmatically load large volumes of records into Zendesk in a controlled,
    asynchronous wayideal for migrations, initial seeding, or ongoing syncs. You submit a file or batched payload,
    define which object type to import (for example, users/organizations/tickets in Support or leads/contacts/deals in
    Sell), and map fields. The import runs as a background job you can monitor via status endpoints, with progress,
    per-row validation, and detailed error reporting.
- aid: zendesk:incremental
  name: Zendesk Incremental API
  tags:
  - Incremental
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/ticket-management/incremental_exports/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/ticket-management/incremental_exports/
    type: Documentation
  - url: openapi/incremental-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Incremental API lets you export only the records that have changed since a specific point in time,
    making it easy to keep external systems in sync without repeatedly pulling full datasets. It supports core objects
    such as tickets, users, organizations, and ticket events, returning results in chronological order along with a
    checkpoint (an end_time or a cursor) you store and use on your next request to continue exactly where you left
    off.
- aid: zendesk:job-statuses
  name: Zendesk Job Statuses
  tags:
  - Jobs
  - Statuses
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/ticket-management/job_statuses/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/ticket-management/job_statuses/
    type: Documentation
  - url: openapi/job-statuses-openapi-original.yml
    type: OpenAPI
  description: >-
    Zendesk Job Statuses is the mechanism and API resource that tracks long-running, asynchronous tasks kicked off in
    Zendesksuch as bulk ticket updates, user or organization imports, and other create/update many operations. Instead
    of waiting for a synchronous response, these endpoints return a job ID that you can poll to see whether the work
    is queued, in progress, or completed, along with progress counts, result details, and any errors.
- aid: zendesk:locales
  name: Zendesk Locales API
  tags:
  - Locales
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/account-configuration/locales/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/account-configuration/locales/
    type: Documentation
  - url: openapi/locales-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Locales API is a read-only service that lets you discover which languages and regional variants
    Zendesk supports and which are enabled on your account. It provides lists of all supported locales, the subsets
    available to end users and to agents, and the current users locale, along with metadata such as the locale code
    (for example, en-US), display name, and whether the language is right-to-left.
- aid: zendesk:macros
  name: Zendesk Macros API
  tags:
  - Macros
  image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
  baseURL: https://{subdomain}.zendesk.com
  humanURL: https://developer.zendesk.com/api-reference/ticketing/business-rules/macros/
  properties:
  - url: https://developer.zendesk.com/api-reference/ticketing/business-rules/macros/
    type: Documentation
  - url: openapi/macros-openapi-original.yml
    type: OpenAPI
  description: >-
    The Zendesk Macros API lets you programmatically manage the reusable, predefined actions that agents apply to
    Support tickets. With it, y

# --- truncated at 32 KB (132 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/zendesk/refs/heads/main/apis.yml