This is a Ruby wrapper for the Harvest API.
gem install harvested
harvest = Harvest.client(subdomain: 'yoursubdomain', username: 'yourusername', password: 'yourpassword')
harvest.projects.all # list out projects
client = Harvest::Client.new(:name => "Billable Company LTD.")
client = harvest.clients.create(client)
harvest.clients.find(client.id) # returns a Harvest::ClientYou can also pass query options in as the last parameter on any object's all finder
method, for example to find all the projects for client ID 12345:
harvest = Harvest.client(subdomain: 'yoursubdomain', username: 'yourusername', password: 'yourpassword')
harvest.projects.all(nil, :client => 12345)Note: the first parameter is a User ID field that is optional, but needs to be specified as nil if not included.
You can pass in any hash of query attributes you wish as per the Harvest API page.
You can find more examples in /examples and in the documentation for Harvest::Base
For most operations you need to be an Admin on the Harvest account. You can do a few select things as a normal user or a project manager, but you will likely get errors.
The team at Harvest built a great API, but there are always dangers in writing code that depends on an API. For example: HTTP Timeouts, Occasional Bad Gateways, and Rate Limiting issues need to be accounted for.
Using Harvested#client your code needs to handle all these situations. However you can also use Harvested#hardy_client which will retry errors and wait for Rate Limit resets.
harvest = Harvest.hardy_client(subdomain: 'yoursubdomain', username: 'yourusername', password: 'yourpassword')
harvest.projects.all # This will wait for the Rate Limit reset if you have gone over your limitHarvested's tests currently support Ruby version 2.0+
My name is Zach Moazeni. I work for an awesome company. And we're hiring!
If you find what looks like a bug:
- Check the GitHub issue tracker to see if anyone else has had the same issue. http://github.com/zmoazeni/harvested/issues/
- If you don’t see anything, create an issue with information on how to reproduce it.
If you want to contribute an enhancement or a fix:
- Fork the project on github http://github.com/zmoazeni/harvested
- Make your changes with tests
- Commit the changes without messing with the Rakefile, or Version
- Make an entry to HISTORY.md
- Send me a pull request
Note on running tests: most specs run against a live Harvest account. To run the suite, sign up for a free trial account and fill out /spec/support/harvest_credentials.yml (a sample harvest_credentials.example.yml has been included).
DO NOT USE YOUR NORMAL CREDENTIALS IN /spec/support/harvest_credentials.yml!!! The test suite blasts all the data before running (similiar to DatabaseCleaner).
The tests use VCR to cache the API responses. This is a great boon for running the tests offline. While uncommon, sometimes the Harvest API will send an erroneous response, VCR will cache it, and subsequent runs will use the incorrect cached response. In order to clear the cached responses, you can run the specs with the VCR_REFRESH environmental variable set to true (e.g. VCR_REFRESH=true bundle exec rake spec).
Estimates aren't currently supported due to the lack of an API. If this opens up, harvested will include them.