Campaign Monitor Rewrites API, Dumps SOAP

Justin Houk
Dec. 13 2010, 12:00AM EST

Campaign Monitor, the email marketing software aimed at designers, recently announced a massive API update that is sure to please developers. The changes are less of an update and more of a complete redesign from the ground up. The folks down in Sydney have gone RESTful, the new version no longer supporting SOAP. The API also added realtime tracking and integrated powerful segmentation tools.

We first wrote about Campaign Monitor back in march as part of our Site in a Box Series. Since then the API has really exploded in popularity. "Our API is getting pretty darn popular these days with 70 requests per second, which grows considerably during our busiest times," wrote co-founder David Greiner in a blog post announcing V3 of its API. "Yeah that number blew me away too." It's hard not to feel the same way.

Probably the biggest news from a developers standpoint is that the API is 100% RESTful and supports different languages through officially released wrappers. Previously some of the API was available as REST, though it was hardly true to the strict definition. Also, some of the functions in V2 of the API were only available as SOAP. Now, SOAP is gone. And, sticking with the times, the service added JSON as a response format, in addition to XML.

One can now access the real-time history of campaign subscribers through the API. Each time someone clicks or performs another 'trackable' action from a campaign email the information is recorded. This includes the ip address of the subscriber that could be used for geolocation. Tools for aggregating these results can also be accessed through the API.

Segmentation is basically grouping email subscribers into subgroups based on rules. Developers can now create and administrate these rules from the API and their own code.

Other updates include:

  • Importing multiple subscribers in batch
  • Monthy billing thought the api
  • Draft Handling
  • Paged Results

Those changes should give developers much to chew on. If that isn't enough the API documentation pages have been completely revamped, a sure sign that the company sees it's API and developers as an important part of it's future.

Justin Houk

Comments

User HTML

  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.