API Release Notes | October 2013

We deployed the October update to the Constant Contact v2 API on October 3, 2013. We’re really excited because this release is packed with all kinds of new stuff!

New Features

What’s new in this API release:

New MyLibrary APIs

The MyLibrary APIs provide developers access to the upgraded MyLibrary Plus product that was just released to all Constant Contact users earlier this week. Click the links to get full documentation for each endpoint. All endpoints are available in our IO Docs API tester, too.

  • MyLibrary information endpoint – retrieves a report that includes disk space usage and file counts.
    uri – https://api.constantcontact.com/v2/library/info
  • Folders collection endpoint – manage the MyLibrary folder collection (GET, POST)
    uri – https://api.constantcontact.com/v2/library/folders
  • Individual Folder endpoint – GET, PUT, DELETE specific folders
    uri – https://api.constantcontact.com/v2/library/folders/{folderId}
  • Trash folder endpoint – GET, DELETE files in the Trash folder
    uri – https://api.constantcontact.com/v2/library/folders/trash/files
  • Files collection endpoint – GET the library file collection, with several available filtering and sorting options
    uri – https://api.constantcontact.com/v2/library/files
  • File collection by folder endpoint – Retrieve files in a specific folder, with several available filtering and sorting options
    uri – https://api.constantcontact.com/v2/library/folders/{folderId}/files
  • Individual file endpoint – GET, PUT, DELETE a specific file
    uri – https://api.constantcontact.com/v2/library/files/{fileId}
  • Add a File – multipart POST endpoint – add a file to the library using a multipart POST
    uri – https://api.constantcontact.com/v2/library/files
  • File upload status endpoint – get upload status report for one or more files
    uri – https://api.constantcontact.com/v2/library/files/uploadstatus/{fileId1,fileId2…fileIdn}
  • Move files endpoint – move files from one folder to another

    uri – https://api.constantcontact.com/v2/library/folders/{folderId}/files

BETA release of EventSpot APIs

The EventSpot APIs are available as BETA starting October 3, 2013. Our customers use EventSpot to manage their events online – fundraisers, online meetings, webinars, conferences, tradeshows, classes and more.

BETA means a couple of things:

  1. The EventSpot APIs are not officially supported and their payloads are subject to change without notice.
  2. We’re looking to you to help us make them better – use them, and tell us how to improve these endpoints so that they’re even easier work with!

Here are the BETA EventSpot APIs, follow the links to full documentation for each endpoint. All endpoints are available in our IO Docs API tester, too.

Bug Fixes

Here are the bugs fixed in this release. Unless otherwise noted, bug fixes apply to the v2 APIs.

Email Campaign tracking_summary

We have added a new Boolean parameter, updateSummary, to the Email Campaign Tracking Summary  and Individual Email Campaign endpoints. when updateSummary=true triggers a tracking_summary update, and the system returns up-to-the-minute data  in the response. Otherwise, the tracking_summary data returned  is as of the last regularly scheduled update.

User documentation improvements

The API user documentation now includes a JSON Response structures for endpoints where the response structure is significantly different from the POST or PUT JSON request structure, as it is for GET Email Campaign Collection.

We have removed the last_sent_date parameter that was erroneously included in the Individual Email Campaign GET user documentation.

The Email Campaign Collection Post user documentation now includes a section on how to Resend an Email Campaign .

Parameters not supported in redirect uri’s

The API Keys and Authentication user documentation now provides clearer information that parameters are not supported in a redirect URI.

V1 API – Contacts

The team fixed a bug that was causing the V1 API to send an incorrect 204 response when a user attempted to update a contact’s email address to one already used by another contact. Now the correct 409 response is sent. In both cases, the API operated correctly by not updating the contact. This occurred with accounts using the legacy contact management system and the V1 API.

Leave a Comment