The Yammer Ruby Gem

A Ruby wrapper for the Yammer REST APIs

This was originally forked from http://github.com/roadly/yammer. I had to rename it due to namespace collisions with the latest Yam gem(which really users Yammer modules)

gem install yapper

Renames Yammer gem to Yapper Updates the dependency on Yam gem to latest: 2.1.1

See HISTORY.md for more

You should probably be using Omniauth(http://github.com/intridea/omniauth), cuz its awesome, and be following that flow. Ryan Bate's excellent RailsCasts are also a great reference: http://railscasts.com/episodes/236-omniauth-part-2

Whatever controller handles the callback, you will have access to a "credentials" key in the oauth object which has an "expires" key, and a "token" key. I stash that entire object in a serialized string in my Authentication model. This token is what you will need.

token = current_user.authentications.find_by_provider("yammer").credentials.token
yam = Yammer.new(oauth_token: token)

That's it!

yam.groups
yam.users

• Specs, specs and specs ... we lack tests even basic ones.
• Support for the following APIs
  • Likes
  • Topics
  • Users
  • Group Memberships
  • Networks

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

Here are some ways you can contribute:

• by using alpha, beta, and prerelease versions
• by reporting bugs
• by suggesting new features
• by writing or editing documentation
• by writing tests
• by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
• by refactoring code
• by closing issues
• by reviewing patches

All contributors will be added to the HISTORY file and will receive the respect and gratitude of the community.

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 issue 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.

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. Commit and push your changes.
7. 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 (c) 2011, Peter Philips <pete <-at-> p373.net> See LICENSE for details.