We’ve been eagerly awaiting the arrival of a CheddarGetter open-source C# wrapper for the benefit of all of our .Net pals out there. Thanks to John at Confer, we can all relax. Seriously, my shoulders just left my earlobes.

John wrote a post that clearly illustrates usage of his offering to the reoccurring billing community. The code is clear and well commented throughout. The implementation is very clean and straightforward. We’re quite happy to list it as a member of our wrapper page.

Confer offers a very slick collaboration app hosted in the cloud. Intra-office social networking, customer & contact tracking, activity tracking and file management are all provided via a very well put together interface.

Ok, let’s be honest, I never really was any good at following directions. That’s probably why I’m an entrepreneur today. That’s also why I spent a few hours trying to find out why I kept getting this error when trying to talk to the CampaignMonitor API in the most basic way:

(101) Invalid ListID

Ok, yeah I didn’t read every line of the documentation. I’ve worked with countless API’s in the past and continue to do so. They’re all very simple on the surface but they all have their little nuances. It turns out that the CM API has one of the most annoying quirks that I’ve ever seen.

I’ll start at the beginning. I decided I wanted to use the API to add subscribers to a list on CM. That’s pretty straightforward, I thought. You know, some sort of authentication mechanism, then provide the email address in some REST-ful way. I glanced at the docs to see that there is a SOAP interface. I quickly decide on that since usually this bloated way of interacting with a simple API is the quickest to code. So, I fire up a SoapClient and throw the four parameters at it and I get that 101 error. Again and again, I try every different way I can think of. Same 101 error.

During the pulling-out-hair stage, I ran across this post: Using Zend_Soap_Client with the Campaign Monitor API which pointed toward the need for a special input header. That prompted me to write a wrapper. I’ll get to that in a sec. It turns out that the input header wasn’t required after all.

When I glanced at the CM API documentation, I saw that there are 3 parameters required for the Subscriber.Add call: ApiKey, ListID, Email. Easy enough. It took a sec to find the ApiKey. The Email parameter is easy. So is the ListID, or so I thought. To find that, I just clicked on the list name in the CM gui and then there, in the address bar, was exactly what I was looking for:

Nope. Its a ListID but not the ListID. No, I had to click on the “edit list name/type” link to find that. What a waste of half a day.

Alright, I’m done blaming CampaignMonitor for my inability to RTFM. I wrote a very quick wrapper around the Zend_Soap_Client class specifically for CampaignMonitor API oddities. Hopefully this will save someone else some headache. Download it here:

CampaignMonitor.php

Use it like so:

$cm = new CG_CampaignMonitor('yourApiKey', 'yourListID');
$result = $cm->AddSubscriber(array('Email'=>'test@example.com', 'Name'=>'Test Subscriber'));

Neither GainStudio nor FeedMagnet will be spending months building a billing application. That’s good because CheddarGetter already did. Instead, they’ve provided the CheddarGetter open source community with two more API wrappers, a simpler task by a long shot.

FeedMagnet’s PyCheddar is a Django compatible Python offering by Jason Ford and Luke Sneeringer designed to closely emulate Django models. Get it from GitHub here. Also available at PyPi. FeedMagnet is a social media aggregation, filtering and moderation engine. Follow them on Twitter @feedmagnet.

Hans at GainStudio recently wrote and released the initial version of yet another cleverly named library, cheddarsnake, a Python wrapper. GainStudio is a project and facility management tool for recording studios, audio-visual studios, advertising departments, and editing and post-production facilities. Follow them on Twitter @gainstudio.

More information about the CheddarGetter API is here.