Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
OmniAuth Strategy for Constant Contact using OAuth2
tree: 3222701b77
Failed to load latest commit information.
lib version bump
spec bugfix part 1
.gitignore Initial commit
.travis.yml hope it works now
Gemfile hope it works now
Guardfile Initial commit
LICENSE Initial commit revert to xml
Rakefile Initial commit
omniauth-constantcontact2.gemspec loosen up multi_json dependency


This gem is an OmniAuth 2.0 Strategy for the ConstantContact API

It supports the OmniAuth REST API which uses OAuth 2.0

Many thanks to Caleb Clark for writing the original OmniAuth strategy. This builds on his work.


Add this line to your application's Gemfile:

gem 'omniauth-constantcontact2'

And then execute:

$ bundle

Or install it yourself as:

$ gem install omniauth-constantcontact2


Then integrate the strategy into your middleware:

use OmniAuth::Builder do
  provider :constantcontact, ENV['CC_KEY'], ENV['CC_SECRET']

In Rails, you'll want to add to the middleware stack:

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :constantcontact, ENV['CC_KEY'], ENV['CC_SECRET']

** Ensure that you have provided the correct Redirect URI in Constant Contact when you generated the Key. You are likely to see an error stating "invalid redirect" if the Request URI does not match the one from your environment.

In development for example the Redirect URI is


You will have to put in your consumer key and secret, which you can find at

For additional information, refer to the OmniAuth wiki.


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request


Copyright (c) 2012 Aditya Sanghi. See LICENSE for details.

Something went wrong with that request. Please try again.