Zendesk

Zendesk Brands API

The Brands API from Zendesk — 4 operation(s) for brands.

Documentation GitHub OpenAPI

Operations 7

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /api/v2/brands List all brands · Zendesk Get Api V2 Brands #

Ask an LLM

“What brands are set up in our Zendesk account?”

“Which brands can an agent without the assign-to-any-brand permission see?”

Tell an agent

List all brands in our account sorted by name.

Show me every brand we support tickets for.

POST /api/v2/brands Create a brand · Zendesk Post Api V2 Brands #

Ask an LLM

“How do I add a new brand for a separate product line?”

“Can I create a brand with its own subdomain through the API?”

Tell an agent

Create a new brand called Acme Outdoor with subdomain acmeoutdoor.

Add a brand for our new product line.

GET /api/v2/brands/{brand_id} Get a brand's details · Zendesk Get Api V2 Brands Brand_id #

Ask an LLM

“How can I see one brand's settings, like its subdomain and logo?”

“What details are returned for a single brand?”

Tell an agent

Show the details of the Acme Outdoor brand.

Get that brand's subdomain and host mapping.

PUT /api/v2/brands/{brand_id} Update a brand or its logo · Zendesk Put Api V2 Brands Brand_id #

Ask an LLM

“Can I upload a new logo image for a brand?”

“How do I change a brand's name or host mapping?”

Tell an agent

Update the Acme Outdoor brand's logo with this image file.

Rename that brand and change its host mapping.

DELETE /api/v2/brands/{brand_id} Delete a brand · Zendesk Delete Api V2 Brands Brand_id #

Ask an LLM

“Can I delete a brand we've retired?”

“Who is allowed to remove a brand from the account?”

Tell an agent destructive · confirm first

Delete the retired Legacy brand.

Remove that brand from our account.

GET /api/v2/brands/{brand_id}/check_host_mapping Validate host mapping for an existing brand · Zendesk Get Api V2 Brands Brand_id Check_host_mapping #

Ask an LLM

“Is the custom domain on one of my existing brands set up correctly?”

“How do I verify the CNAME for a brand that already exists?”

Tell an agent

Check whether the Acme Outdoor brand's host mapping is valid.

Verify the custom domain configured on that existing brand.

GET /api/v2/brands/check_host_mapping Validate a host mapping before creating a brand · Zendesk Get Api V2 Brands Check_host_mapping #

Ask an LLM

“Before creating a brand, can I test whether a host mapping works for a subdomain?”

“Will support.example.com be a valid host mapping for a given subdomain?”

Tell an agent

Check if support.example.com is a valid host mapping for the subdomain I plan to use.

Test a host mapping and subdomain pair ahead of creating a new brand.

Documentation

https://developer.zendesk.com/api-reference/ticketing/introduction/

https://developer.zendesk.com/api-reference/ticketing/targets/targets/

https://developer.zendesk.com/api-reference/sales-crm/resources/account/

https://developer.zendesk.com/api-reference/ticketing/tickets/activity_stream/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/channel_framework/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket-attachments/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/

https://developer.zendesk.com/api-reference/ticketing/organizations/organizations/

https://developer.zendesk.com/api-reference/ticketing/business-rules/automations/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/bookmarks/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/brand_agents/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/brands/

https://developer.zendesk.com/api-reference/live-chat/chat-api/chats/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/

https://developer.zendesk.com/api-reference/custom-data/introduction/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/custom_roles/

https://developer.zendesk.com/api-reference/ticketing/tickets/custom_ticket_statuses/

https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/

https://developer.zendesk.com/api-reference/ticketing/users/users/

https://developer.zendesk.com/api-reference/ticketing/business-rules/deletion_schedules/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/dynamic_content/

https://developer.zendesk.com/api-reference/ticketing/tickets/email_notifications/

https://developer.zendesk.com/api-reference/ticketing/groups/group_memberships/

https://developer.zendesk.com/api-reference/ticketing/business-rules/group_sla_policies/

https://developer.zendesk.com/api-reference/ticketing/groups/groups/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_import/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/incremental_exports/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/job_statuses/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/locales/

https://developer.zendesk.com/api-reference/ticketing/business-rules/macros/

https://developer.zendesk.com/api-reference/ticketing/oauth/oauth_tokens/

https://developer.zendesk.com/api-reference/ticketing/organizations/organization_fields/

https://developer.zendesk.com/api-reference/ticketing/organizations/organization_memberships/

https://developer.zendesk.com/api-reference/ticketing/organizations/organization_subscriptions/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/push_notification_devices/

https://developer.zendesk.com/api-reference/agent-availability/omnichannel_routing_queues/omnichannel_routing_queues/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/support_addresses/

https://developer.zendesk.com/api-reference/ticketing/lookup_relationships/lookup_relationships/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket-requests/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/resource_collections/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/skill_based_routing/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/satisfaction_ratings/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/satisfaction_reasons/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/search/

https://developer.zendesk.com/api-reference/ticketing/account-configuration/sessions/

https://developer.zendesk.com/api-reference/ticketing/tickets/sharing_agreements/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_skips/

https://developer.zendesk.com/api-reference/ticketing/business-rules/sla_policies/

https://developer.zendesk.com/api-reference/ticketing/tickets/suspended_tickets/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/tags/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_fields/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_form_statuses/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_forms/

https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_metrics/

https://developer.zendesk.com/api-reference/ticketing/business-rules/triggers/

https://developer.zendesk.com/api-reference/ticketing/business-rules/views/

https://developer.zendesk.com/api-reference/ticketing/ticket-management/workspaces/

Specifications

https://raw.githubusercontent.com/api-evangelist/zendesk/refs/heads/main/openapi/zendesk-brands-api-openapi.yml

Schemas & Data

https://raw.githubusercontent.com/api-evangelist/zendesk/refs/heads/main/json-schema/zendesk-ticket-schema.json

https://raw.githubusercontent.com/api-evangelist/zendesk/refs/heads/main/json-schema/zendesk-user-schema.json

Other Resources

https://raw.githubusercontent.com/api-evangelist/zendesk/refs/heads/main/json-ld/zendesk-context.jsonld

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/zendesk:zendesk-brands-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  version: '1.0'
  title: Zendesk Brands API
  description: Needs a description.
tags:
- name: Brands
paths:
  /api/v2/brands:
    get:
      operationId: ListBrands
      tags:
      - Brands
      summary: Zendesk Get Api V2 Brands
      description: 'Returns a list of all brands for your account sorted by name.


        #### Allowed for


        * Admins

        * Agents with the `assign_tickets_to_any_brand` permission can list all brands for the account

        * Agents without the `assign_tickets_to_any_brand` permission can only list brands they are members of


        #### Pagination


        * Cursor pagination (recommended)

        * Offset pagination


        See Pagination.'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BrandsResponse'
              examples:
                default:
                  $ref: '#/components/examples/BrandsResponseExample'
    post:
      operationId: CreateBrand
      tags:
      - Brands
      summary: Zendesk Post Api V2 Brands
      description: '#### Allowed for

        - Admins'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BrandCreateRequest'
            examples:
              default:
                $ref: '#/components/examples/BrandCreateRequestExample'
      responses:
        '201':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BrandResponse'
              examples:
                default:
                  $ref: '#/components/examples/BrandResponseExample'
  /api/v2/brands/{brand_id}:
    get:
      operationId: ShowBrand
      tags:
      - Brands
      summary: Zendesk Get Api V2 Brands Brand_id
      description: 'Returns a brand for your account.


        #### Allowed for


        * Admins, Agents'
      parameters:
      - $ref: '#/components/parameters/BrandId'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BrandResponse'
              examples:
                default:
                  $ref: '#/components/examples/BrandResponseExample'
    put:
      operationId: UpdateBrand
      tags:
      - Brands
      summary: Zendesk Put Api V2 Brands Brand_id
      description: 'Returns an updated brand.


        #### Allowed for

        * Admins


        #### Updating a Brand''s Image

        A brand image can be updated by uploading a local file using the update brand endpoint. See the **Using curl** sections below for more information.'
      parameters:
      - $ref: '#/components/parameters/BrandId'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BrandUpdateRequest'
            examples:
              default:
                $ref: '#/components/examples/BrandUpdateRequestExample'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BrandResponse'
              examples:
                default:
                  $ref: '#/components/examples/BrandResponseExample'
            image/jpg: {}
            image/png: {}
    delete:
      operationId: DeleteBrand
      tags:
      - Brands
      summary: Zendesk Delete Api V2 Brands Brand_id
      description: 'Deletes a brand.


        #### Allowed for

        - Admins'
      parameters:
      - $ref: '#/components/parameters/BrandId'
      responses:
        '204':
          description: No Content response
  /api/v2/brands/{brand_id}/check_host_mapping:
    get:
      operationId: CheckHostMappingValidityForExistingBrand
      tags:
      - Brands
      summary: Zendesk Get Api V2 Brands Brand_id Check_host_mapping
      description: 'Returns a JSON object determining whether a host mapping is valid for the given brand.


        #### Allowed for

        - Admins'
      parameters:
      - $ref: '#/components/parameters/BrandId'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HostMappingObject'
              examples:
                default:
                  $ref: '#/components/examples/HostMappingResponseValidExample'
                invalidCNAMEExample:
                  $ref: '#/components/examples/HostMappingResponseInvalidCNAMEExample'
                wrongCNAMEExample:
                  $ref: '#/components/examples/HostMappingResponseWrongCNAMEExample'
  /api/v2/brands/check_host_mapping:
    get:
      operationId: CheckHostMappingValidity
      tags:
      - Brands
      summary: Zendesk Get Api V2 Brands Check_host_mapping
      description: 'Returns a JSON object determining whether a host mapping is valid for a given subdomain.


        #### Allowed for


        * Admins'
      parameters:
      - $ref: '#/components/parameters/HostMapping'
      - $ref: '#/components/parameters/Subdomain'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HostMappingObject'
              examples:
                default:
                  $ref: '#/components/examples/HostMappingResponseValidExample'
                invalidCNAMEExample:
                  $ref: '#/components/examples/HostMappingResponseInvalidCNAMEExample'
                wrongCNAMEExample:
                  $ref: '#/components/examples/HostMappingResponseWrongCNAMEExample'
components:
  schemas:
    BrandsResponse:
      title: Brands
      type: object
      allOf:
      - $ref: '#/components/schemas/OffsetPaginationObject'
      - type: object
        properties:
          brands:
            type: array
            description: Array of brands
            items:
              $ref: '#/components/schemas/BrandObject'
    HostMappingObject:
      title: Host Mapping
      type: object
      properties:
        cname:
          type: string
          description: The canonical name record for a host mapping
        expected_cnames:
          type: array
          description: Array of expected CNAME records for host mapping(s) of a given brand
          items:
            type: string
        is_valid:
          type: boolean
          description: Whether a host mapping is valid or not for a given brand
        reason:
          type: string
          description: Reason why a host mapping is valid or not
      example:
        cname: google.com
        expected_cnames:
        - bar.zendesk.coom
        is_valid: false
        reason: wrong_cname
    BrandResponse:
      type: object
      properties:
        brand:
          $ref: '#/components/schemas/BrandObject'