Part 1: Welcome to the Zendesk platform
Welcome to the Zendesk Platform!
If you don't know what that means, you're in the right place. This guide was created to help the large number of non-technical people looking to build on our platform. We understand that the idea of coding, especially when you've never written a single line, may be daunting and scary, but this guide will break it down, step by step, ensuring that you not only understand our API and platform, but you'll actually learn how to code along the way. We hope you're excited and ready to learn!
This tutorial is part of a 4-part series. Use the link at the end of the article to go to part 2. The tutorial also assumes you use a Mac and Chrome as your browser.
Disclaimer: Zendesk provides this article for instructional purposes only. Zendesk does not provide support for the content. Please post any issue in the Zendesk APIs community or search for a solution online.
A computer platform, in it’s most basic sense, is the pre-existing environment that computer software is designed to work with. For example, Twitter is a service almost everyone is familiar with. You can create tweets, retweet, and follow people. Twitter is a platform that then allows people to build on top of and manipulate to fit their needs. You want a bot that follows every account that has “cats” in the name? You can do that because of their platform.
By the end of this guide, you'll have done the following:
- Learned about Rest APIs, requests, and cURL statements
- Installed Sublime Text to edit and save our code
- Set up a developer environment on your computer to build apps
- Worked your way through our most commonly used APIs and authentication
- Created a Github repo of scripts, built by you
- Created and populated a robust test account
To understand what an API is, first let's think about a technical product we all use, like Zendesk Support. Support is a piece of software that brings companies and their customers closer together. There are many things that Support lets you do, such as:
- Create tickets
- Add & update users
- Create groups
- Suspend users
- Mark comments as private
- Customize your Help Center
- And much more
All of these actions that Zendesk Support can do are part of our API. Simply put, an API is a group of things that software can do. (See, that's not scary to understand.) By accessing an API, you have the power to do all of these things too!
Before building with our API, you'll want to read our overview of Restrictions and Responsibilities, which you'll find here: Restrictions and Responsibilities.
You'll want to be familiar with this later on when you decide to build something for real.
Our API is a RESTful one. You can read the deep deep details of REST here, but for the purposes of this tutorial and getting started, here's what you need to know:
REST stands for Representational State Transfer. It is sometimes spelled "ReST"
You'll see verbs or terms like GET, PUT, POST, and DELETE (written just like that, all caps)
These terms are also known as HTTP methods or protocol (sometimes just HTTP)
Think of them like so:
What you want to do Method to use Create POST Retrieve GET Update PUT Delete DELETE
HTTP protocol is used to make calls between machines by sending requests to GET information or DELETE data
After a request is made, the computer returns a response in JSON
Depending on how you make the request (and we’ll talk more on that in a bit) and the API itself, you’ll need the following information:
Subdomain - The subdomain is another term for your Zendesk Support account. When you sign up for a Support account, you're asked to create a subdomain. Our support subdomain is ‘support’, and when entered, it formats like so:
Email - Your email address used with Zendesk Support
Password - Your Zendesk Support password
API token - You can use an API token instead of your password. API tokens are managed in the Admin Center interface at Apps and integrations > APIs > Zendesk APIs. The page lets you view, add, or delete tokens. More than one token can be active at the same time. Deleting a token deactivates it permanently.
If using an API token, use the following authentication format:
JSON is a syntax for storing and exchanging data. In other words, it's a language and format used to send and receive information
JSON is structured like so:
- Open up a new browser window or tab.
Sign in to your Support instance at
Your "subdomain" is your Support account name. For example, my subdomain is 'catzomg' (because that's what I registered), so I enter that as my subdomain and get
Be sure to delete the curly braces. They're not needed to run the call.
Once signed in, go to
Voila, you just made a call to the Zendesk Support API and got your account info!
If you're curious about what just happened, right click the web page and click Inspect Element. If you aren't on Chrome, I suggest switching to it so you can follow along without issues.
With Inspect Element, a developer console pops up on the bottom of your web page. Navigate to the Network tab and click it. It'll look like this:
Refresh your page. In the Network tab, you’ll see your completed request:
Once you feel comfortable with the information in this part, be sure to continue on with Part 2: Reading JSON, installing cURL, and completing your developer setup.