user_name? password? huh... really? about constant_contact HOT 5 CLOSED

You set the key with ConstantContact::Base.api_key = KEY_HERE

The user and password are indeed the username and password of the Constant Contact account you want to access. Unfortunately, that was the only acceptable authentication method at the time this library was written (see: http://developer.constantcontact.com/doc/authenticationOverview). Now I see that as of November 2010, they support OAuth! I'll create an issue for this. Maybe you (or someone else) can give a hand in implementing OAuth.

from constant_contact.

Well I have implemented oauth, consumer and provider into two apps last week. Active Resource isn't really that compatible. So that may mean a whole new connection module for you to write, and hopefully then that won't affect the other classes you have got there.

from constant_contact.

I think it can be done in a compatible way, as described in https://github.com/idris/constant_contact/issues#issue/6/comment/747265

from constant_contact.

I just went with mailchimp for now. Take a look at hominid for a gem that just works and is easy to understand. fwiw. Not that this isn't, but going down this path wasn't as easy as it is with Hominid.

from constant_contact.

True, I use hominid also for Mailchimp and it's great. I actually didn't start this library, I just forked it and made it a gem (it looks like this is the only active fork). Mailchimp's APIs are a lot better than Constant Contact's (in my opinion), and so it's easier to write a nice library for it. Constant Contact's API uses XML Atom Feeds, and is a great candidate for ActiveResource, which does all of the heavy lifting. That's why this library uses ActiveResource, rather than a more custom interface like Hominid's.

from constant_contact.