Project

silverpop

0.01
No commit activity in last 3 years
No release in over 3 years
A Ruby wrapper for the SilverPop API
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

Runtime

~> 3.0
~> 0.9.0
~> 3.4
~> 0.5
 Project Readme

SilverPop API

A Ruby wrapper for the SilverPop API

[Build Status][travis] [travis]: http://travis-ci.org/upworthy/silverpop

Installation

$ gem install silverpop

Documentation

http://rdoc.info/gems/silverpop

Usage Examples

require 'silverpop'
require 'oauth2'

#Generate your OAuth2 access token
client = OAuth2::Client.new(SILVERPOP_CLIENT_ID, SILVERPOP_CLIENT_SECRET, site: "https://api1.silverpop.com/oauth/token")
access_token = OAuth2::AccessToken.from_hash(client, refresh_token: SILVERPOP_REFRESH_TOKEN).refresh!

@client = SilverPop.new({access_token: access_token.token, url: "https://api1.silverpop.com"})

#add_recipeint
#pass in user variables, database contact list, and contact list id
a = @client.add_recipient({email:"test@example.com"}, 123, [456])
resp.Envelope.Body.RESULT.SUCCESS # => "TRUE"

Contributing

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 specifications
  • by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
  • by refactoring code
  • by fixing issues
  • by reviewing patches

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. 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 repository.
  2. Create a topic branch.
  3. Add specs for your unimplemented feature or bug fix.
  4. Run bundle exec rake spec. If your specs pass, return to step 3.
  5. Implement your feature or bug fix.
  6. Run bundle exec rake spec. If your specs fail, return to step 5.
  7. Run open coverage/index.html. If your changes are not completely covered by your tests, return to step 3.
  8. Add documentation for your feature or bug fix.
  9. Run bundle exec rake yard. If your changes are not 100% documented, go back to step 8.
  10. Add, commit, and push your changes.
  11. Submit a pull request.

Copyright

Copyright (c) 2013 Upworthy. See LICENSE for details.