Ruby wrapper for the TradeHill API

TradeHill is a Bitcoin exchange that supports 26 currencies.

Installation

gem install tradehill

Alias

After installing the gem, you can get the current price for 1 BTC in USD by typing btc in your bash shell simply by setting the following alias:

alias btc='ruby -r rubygems -r tradehill -e "puts TradeHill.ticker.last"'

Documentation

http://rdoc.info/gems/tradehill

Continuous Integration

Build Status

Usage Examples

require 'rubygems'
require 'tradehill'

# Fetch open asks
puts TradeHill.asks

# Fetch open bids
puts TradeHill.bids

# Fetch the last 48 hours worth of trades (takes a minute)
puts TradeHill.trades

# Certain methods require authentication
TradeHill.configure do |config|
  config.currency = "USD" # This is the default
  config.name = YOUR_TRADEHILL_USERNAME
  config.pass = YOUR_TRADEHILL_PASSWORD
end

# Get your current balance
puts TradeHill.balance

# Place a limit order to buy one bitcoin for $0.011
TradeHill.buy! 1.0, 0.011

# Place a limit order to sell one bitcoin for $100
TradeHill.sell! 1.0, 100.0

# Cancel order 1234567890
TradeHill.cancel "1234567890"

Contributing

In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

Submitting an Issue

We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issuse by voting it up. When submitting a bug report, please include a Gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.

Submitting a Pull Request

  1. Fork the project.
  2. Create a topic branch.
  3. Implement your feature or bug fix.
  4. Add documentation for your feature or bug fix.
  5. Run bundle exec rake doc:yard. If your changes are not 100% documented, go back to step 4.
  6. Add specs for your feature or bug fix.
  7. Run bundle exec rake spec. If your changes are not 100% covered, go back to step 6.
  8. Commit and push your changes.
  9. Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)

Copyright

Copyright (c) 2011 Erik Michaels-Ober. See LICENSE for details.