Skip to content
GoodData API Ruby Gem
Ruby Other
Latest commit e17d314 Apr 25, 2016 @fluke777 fluke777 Merge pull request #655 from korczis/tma-102.1
TMA-102: Enable pending tests, remove broken
Failed to load latest commit information.
bin Use relative lib, not installed one Mar 2, 2015
spec Merge branch 'develop' of into tma-… Apr 25, 2016
tmp Staging changes ... May 21, 2014
.document Initial commit of the new gooddata-ruby Oct 6, 2010
.gitignore Ignore doc subdirectory May 15, 2015
.rspec rspec global settings Mar 6, 2014
.rubocop.yml Disable Style/SignalException Feb 10, 2016
.yardopts Merge branch 'master' of Mar 19, 2014 Bumping version Apr 15, 2016 Added Mandatory user filters Jan 19, 2015 TRIVIAL: Remove coveralls, update Feb 22, 2016
Gemfile Use terminal-table version from rubygems Jun 29, 2015
Gemfile.lock Remove unused guard gem Apr 25, 2016
Guardfile Add guard-rspec for automated spec runs May 17, 2015
LICENSE Implemented rake license:add task Aug 3, 2015
LICENSE.rb Implemented rake license:add task Aug 3, 2015 TRIVIAL: Update copyright date Nov 2, 2015
Rakefile TMA-98: Fix Jenkins Tests Mar 10, 2016 Few notes Aug 12, 2014 Generate authors info Jan 9, 2015
dependency_decisions.yml TRIVIAL: Update dependency_decisions.yml Feb 22, 2016
gooddata Removed code which was mistakenly commited Apr 29, 2014
gooddata.gemspec Remove unused guard gem Apr 25, 2016

GoodData API Ruby wrapper and CLI

A convenient Ruby wrapper around the GoodData RESTful API. The gem comes in two flavors. It has a CLI client and it is a library which you can integrate into your application.

The best documentation for the GoodData API can be found using these resources:


Gem Version Downloads Dependency Status Code Climate Build Status Coverage Status


If you are using bundler. Add

gem "gooddata"

into Gemfile

and run

bundle install

If you are using gems just

gem install gooddata

Note on Patches/Pull Requests

  • 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 we can ignore when we pull)
  • run rake test and make sure all tests passes
  • run rake cop and make sure you did not introduced any new coding rules issues
  • Send us a pull request. Bonus points for topic branches.


Originaly started by

Pavel Kolesnikov [ / @koles ]

Actively developed and maintained by


For full contributor info see contributors page.

Special thanks to


Copyright (c) 2010 - 2015 GoodData Corporation and Thomas Watson Steen. See LICENSE for details.

Something went wrong with that request. Please try again.