iContact API v2.0

I haven't heard of the v2.0 API, you have any links to the 2.0 version of the API? Also, haven't heard of the contests. If you have any links for the contests too that would be cool.

Greetings:

It's true, we at iContact are about to release a public beta for the new iContact API v2.0.

The new API has been rebuilt from the ground up and implements a RESTful design. The v2.0 API exposes nearly all the iContact capabilities currently exposed in the Web interface as 'resources' which can be manipulated using GET, POST, PUT and DELETE. The new API will be functionally rich, robustly documented, and well-supported.

We're hoping to foster an active and engaged developer community. And to encourage participation in the open beta, we're launching a contest where developers can win cash prizes, have their integration listed in our new Developer Central and be featured in an upcoming iContact newsletter that reaches hundreds of thousands of recipients.

The open beta and contest will launch on April 6, 2009. For all the details, see the iContact API Challenge site here: http://www.icontact.com/apichallenge/

We'd love to have you participate.

Cheers,

Ken

Ken O'Berry
Director of Product Management
iContact
2635 Meridian Pkwy., Ste. 200
Durham, NC 27713

Ken,

Have you announced an EOL on version 1? If so, what is the EOL date?

Looks like it's launched the beta but I can't get access.

James, I see that you are building this as DRUPAL-6--2. How stable is it?

I need to demo with someone who already uses iContact very soon. Right now, I am almost being forced to go with 5.x unless I can solve a calendar problem. If I can't solve that, I may take a shot at backporting the 6.2 branch, unless you have it also for 5.x.

Currently I have not checked in all my local changes back to the DRUPAL-6--2 branch and even still it is mostly only behind the scenes code along with settings pages. The DRUPAL-6--2 branch is also based on the iContact API v2.0 that is currently in Beta.

My current dilemma is how to structure the settings pages. The 2.0 API for iContact's service provides accounts as the base parent, then branches to client folders which branches to contacts (among others). My preferred menu structure was going to be '/admin/icontact/accounts/{account_id}/clientfolders/{clientfolder_id}/contacts/{contact_id}', but Drupal has a MAX_MENU_DEPTH of 7 which makes this solution not a good choice if I want to use menu tabs and/or argument loaders. My next thought was to use '/admin/icontact/accounts/{account_id}' with 'accounts' being either that, 'clientfolders', or 'contacts' and {account_id} being relative to the previous argument. The problem with this is every child of an account needs to know it's {account_id} and each client folder needs to know it's {clientfolder_id}, but these can be provided in $_GET but would require basic checks to make sure their set and such. I'll try to start a new issue to discuss this more.

The 5.x branch works but the feature set is lacking. It provides a rough API for Drupal modules and has a module that implements a subscription block where users can enter contact fields which have been selected by an admin and subscribe the list the admin has chosen. This is as far as I had gotten on the 5.x branch due to it met the needs of my client so funding essentially stopped. The iContact API 2.0 I am writing on my own as I find the time. I'll commit what I have and you can take a look at it if you would like.

Thanks. I suspect my choice is going to be determined by their needs on a calendar (Events is 6.x, but Event Repeat is only 5.x). I honestly know nothing about using iContact, except that the customer is already using it and wants to stay with it, which I understand. So I need to find out if the basic support is adequate or if something more will be needed.

Sounds good. Both the 5.x and 6.x have implemented a working API for Drupal modules so creating additional functionality should be simple enough.

Okay

Hello pbuonaiuto:

We have not yet announced an EOL date for version 1. I will do so following the launch of API v2.0, which should be coming later this month.

Best,

Ken

Ken O'Berry
Director of Product Management
iContact
2635 Meridian Pkwy., Ste. 200
Durham, NC 27713

Hi,
I am using drupal 5 and the iContact module API v1.x but the iContact is using API v2.x. How can i resolve this problem?

The Drupal 5 branch of iContact needs to update how the requests are made to the iContact server. I currently do not have enough time to back port the changes made in the Drupal 6 branch to the Drupal 5 branch. If someone is willing to submit patches, I might be able to find the time to test them. Check out the Coder module to help in back-porting. The biggest hassle in back-porting the 6.x-2.x branch to Drupal 5 is the ability to depend on PHP 5 for SimpleXML.

Closing. Drupal 5.x no longer supported.