This client only supports Zendesk's v2 API. Please see our API documentation for more information.
Please check out the wiki, class documentation, and issues before reporting a bug or asking for help.
- Version 0.0.5 brings with it a change to the top-level namespace. All references to Zendesk should now use ZendeskAPI.
- Version 0.3.0 changed the license from MIT to Apache Version 2.
- Version 0.3.2 introduced a regression when side-loading roles on users. This was fixed in 0.3.4.
- Version 1.0.0 changes the way errors are handled. Please see the wiki page for more info.
- Version 1.3.0 updates the Faraday dependency to 0.9. Since Faraday did not bump a major version we have not either, but there is no guarantee >= 1.3.0 works with Faraday < 0.9
- Version 1.3.8 had a bug where attachments were created, but the response was not handled properly
- Version >= 1.0 and < 1.4.2 had a bug where non application/json response bodies were discarded
The Zendesk API client can be installed using Rubygems or Bundler.
gem install zendesk_apiAdd it to your Gemfile
gem "zendesk_api"
and follow normal Bundler installation and execution procedures.
Configuration is done through a block returning an instance of ZendeskAPI::Client. The block is mandatory and if not passed, an ArgumentError will be thrown.
require 'zendesk_api'
client = ZendeskAPI::Client.new do |config|
# Mandatory:
config.url = "<- your-zendesk-url ->" # e.g. https://mydesk.zendesk.com/api/v2
# Basic / Token Authentication
config.username = "login.email@zendesk.com"
# Choose one of the following depending on your authentication choice
config.token = "your zendesk token"
config.password = "your zendesk password"
# OAuth Authentication
config.access_token = "your OAuth access token"
# Optional:
# Retry uses middleware to notify the user
# when hitting the rate limit, sleep automatically,
# then retry the request.
config.retry = true
# Logger prints to STDERR by default, to e.g. print to stdout:
require 'logger'
config.logger = Logger.new(STDOUT)
# Changes Faraday adapter
# config.adapter = :patron
# Merged with the default client options hash
# config.client_options = { :ssl => false }
# When getting the error 'hostname does not match the server certificate'
# use the API at https://yoursubdomain.zendesk.com/api/v2
endNote: This ZendeskAPI API client only supports basic authentication at the moment.
The result of configuration is an instance of ZendeskAPI::Client which can then be used in two different methods.
One way to use the client is to pass it in as an argument to individual classes.
ZendeskAPI::Ticket.new(client, :id => 1, :priority => "urgent") # doesn't actually send a request, must explicitly call #save
ZendeskAPI::Ticket.create(client, :subject => "Test Ticket", :comment => { :value => "This is a test" }, :submitter_id => client.current_user.id, :priority => "urgent")
ZendeskAPI::Ticket.find(client, :id => 1)
ZendeskAPI::Ticket.destroy(client, :id => 1)Another way is to use the instance methods under client.
client.tickets.first
client.tickets.find(:id => 1)
client.tickets.build(:subject => "Test Ticket")
client.tickets.create(:subject => "Test Ticket", :comment => { :value => "This is a test" }, :submitter_id => client.current_user.id, :priority => "urgent")
client.tickets.destroy(:id => 1)The methods under ZendeskAPI::Client (such as .tickets) return an instance of ZendeskAPI::Collection a lazy-loaded list of that resource. Actual requests may not be sent until an explicit ZendeskAPI::Collection#fetch, ZendeskAPI::Collection#to_a, or an applicable methods such as #each.
Resource updating is implemented by sending only the changed? attributes to the server (see ZendeskAPI::TrackChanges).
Unfortunately, this module only hooks into Hash meaning any changes to an Array not resulting in a new instance will not be tracked and sent.
zendesk_api_client_rb $ bundle console
> a = ZendeskAPI::Trackie.new(:test => []).tap(&:clear_changes)
> a.changed?(:test)
=> false
> a.test << "hello"
=> ["hello"]
> a.changed?(:test)
=> false
> a.test += %w{hi}
=> ["hello", "hi"]
> a.changed?(:test)
=> true
ZendeskAPI::Collections can be paginated:
tickets = client.tickets.page(2).per_page(3)
next_page = tickets.next # => 3
tickets.fetch # GET /api/v2/tickets?page=3&per_page=3
previous_page = tickets.prev # => 2
tickets.fetch # GET /api/v2/tickets?page=2&per_page=3Iteration over all resources and pages is handled by Collection#all
client.tickets.all do |resource|
# every resource, from all pages, will be yielded to this block
endIf given a block with two arguments, the page number is also passed in.
client.tickets.all do |resource, page_number|
# all resources will be yielded along with the page number
endCallbacks can be added to the ZendeskAPI::Client instance and will be called (with the response env) after all response middleware on a successful request.
client.insert_callback do |env|
puts env[:response_headers]
endIndividual resources can be created, modified, saved, and destroyed.
ticket = client.tickets[0] # ZendeskAPI::Ticket.find(client, :id => 1)
ticket.priority = "urgent"
ticket.attributes # => { "priority" => "urgent" }
ticket.save # Will PUT => true
ticket.destroy # => true
ZendeskAPI::Ticket.new(client, { :priority => "urgent" })
ticket.new_record? # => true
ticket.save # Will POSTWarning: this is an experimental feature. Abuse it and lose it.
To facilitate a smaller number of requests and easier manipulation of associated data we allow "side-loading", or inclusion, of selected resources.
For example: A ZendeskAPI::Ticket is associated with ZendeskAPI::User through the requester_id field. API requests for that ticket return a structure similar to this:
"ticket": {
"id": 1,
"url": "http.....",
"requester_id": 7,
...
}Calling ZendeskAPI::Ticket#requester automatically fetches and loads the user referenced above (/api/v2/users/7).
Using side-loading, however, the user can be partially loaded in the same request as the ticket.
tickets = client.tickets.include(:users)
# Or client.tickets(:include => :users)
# Does *NOT* make a request to the server since it is already loaded
tickets.first.requester # => #<ZendeskAPI::User id=...>OR
ticket = client.tickets.find(:id => 1, :include => :users)
ticket.requester # => #<ZendeskAPI::User id=...>Currently, this feature is limited to only a few resources and their associations. They are documented on developer.zendesk.com.
Searching is done through the client. Returned is an instance of ZendeskAPI::Collection:
client.search(:query => "my search query") # /api/v2/search.json?query=...
client.users.search(:query => "my new query") # /api/v2/users/search.json?query=...API endpoints such as tickets/recent or topics/show_many can be accessed through chaining. They will too return an instance of ZendeskAPI::Collection.
client.tickets.recent
client.topics.show_many(:verb => :post, :ids => [1, 2, 3])Use either of the following to obtain the current user instance:
client.users.find(:id => 'me')
client.current_userBulk importing tickets allows you to move large amounts of data into Zendesk.
ticket = ZendeskAPI::Ticket.import(client, :subject => "Help", :comments => [{ :author_id => 19, :value => "This is a comment" }])http://developer.zendesk.com/documentation/rest_api/ticket_import.html
Files can be attached to ticket comments using either a path or the File class and will be automatically uploaded and attached.
ticket = ZendeskAPI::Ticket.new(client, :comment => { :value => "attachments" })
ticket.comment.uploads << "img.jpg"
ticket.comment.uploads << File.new("img.jpg")
ticket.savev1.1.0 introduces support for the Zendesk Apps API
upload = client.apps.uploads.create!(:file => "path/to/app.zip")
client.apps.create!(:name => "test", :upload_id => upload.id)
# Or
app = ZendeskAPI::App.new(client, :name => "test")
app.upload = "path/to/app.zip"
app.save!
# Or
upload = ZendeskAPI::App::Upload.new(client, :file => "path/to/app.zip")
upload.save!
app = ZendeskAPI::App.new(client, :name => "test")
app.upload_id = upload.id
app.save!
# Or
client.apps.create!(:name => "test", :upload => "app.zip")Note: job statuses are currently not supported, so you must manually poll the job status API for app creation.
body = {}
until %w{failed completed}.include?(body["status"])
response = client.connection.get(app.response.headers["Location"])
body = response.body
sleep(body["retry_in"])
endupload = client.apps.uploads.create!(:file => "NewApp.zip")
# Then
client.apps.update!(:id => 123, :upload_id => upload.id)
# Or
app = ZendeskAPI::App.new(client, :id => 123)
app.upload_id = upload.id
app.save!
# Or
ZendeskAPI::App.update!(client, :id => 123, :upload_id => upload.id)client.apps.destroy!(:id => 123)
app = ZendeskAPI::App.new(client, :id => 123)
app.destroy!
ZendeskAPI::App.destroy!(client, :id => 123)install = ZendeskAPI::AppInstallation.new(client, :app_id => 123)
install.save!
client.apps.installations.create!(:app_id => 123)
ZendeskAPI::AppInstallation.create!(client, :app_id => 123)apps = client.app.installations
apps.fetch!client.app.installations.update!(:id => 123, :settings => { :title => "My New Name" })
install = ZendeskAPI::AppInstallation.new(client, :id => 123)
install.settings = { :title => "My New Name" }
install.save!
ZendeskAPI::AppInstallation.update!(client, :id => 123, :settings => { :title => "My New Name" })client.app.installations.destroy!(:id => 123)
install = ZendeskAPI::AppInstallation.new(client, :id => 123)
install.destroy!
ZendeskAPI::AppInstallation.destroy!(client, :id => 123)- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it. This is important so I don't break it in a future version unintentionally.
- Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
- Send me a pull request. Bonus points for topic branches.
Tested with Ruby 1.9.3, 2.0.0, 2.1.0, and jRuby.
Copyright 2013 Zendesk
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.