Description
Ruby wrapper for the LinkedIn API. The LinkedIn gem provides an easy-to-use wrapper for LinkedIn's REST APIs.
Travis CI :
linkedin alternatives and similar gems
Based on the "Third-party APIs" category.
Alternatively, view linkedin alternatives based on common mentions on social networks and blogs.
-
ruby-gmail
A Rubyesque interface to Gmail. Connect to Gmail via IMAP and manipulate emails and labels. Send email with your Gmail account via SMTP. Includes full support for parsing and generating MIME messages. -
itunes_store_transporter
Upload and manage your assets in the iTunes Store using the iTunes Store’s Transporter (iTMSTransporter). -
pivotal-tracker-api
This is a Ruby Gem that can be used to communicate with the Pivotal Tracker API v5
Scout Monitoring - Performance metrics and, now, Logs Management Monitoring with Scout Monitoring
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of linkedin or a related project?
README
Ruby wrapper for the LinkedIn API. The LinkedIn gem provides an easy-to-use wrapper for LinkedIn's REST APIs.
Installation
gem install linkedin
Documentation
http://rdoc.info/gems/linkedin
Usage
[View the Examples](EXAMPLES.md)
Changelog
[View the Changelog](CHANGELOG.md)
TODO
- Update and correct test suite
- Change to Faraday for authentication
- Implement Messaging APIs
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.
- Make sure your test doesn't just check of instance of LinkedIn::Mash :smile:.
- 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.
Copyright
Copyright (c) 2013-Present Matt Kirk 2009-11 Wynn Netherland. See LICENSE for details.
*Note that all licence references and agreements mentioned in the linkedin README section above
are relevant to that project's source code only.