We are using the v2 API to insert pre-formatted campaigns into Constant Contact for sending. Recent changes to the Constant Contact interface are causing two problems.
When we click on one of our campaigns we get an error about a new editor with an offer to copy the campaign into the new editor. This works but is a lot of extra work for us to send our newsletters. The old campaign remains in the list and has to be manually deleted. This problem appears somewhat intermittent. It happened for a while in December, stopped, and is happening again now.
I'm speculating that the format_type=5 field in the v3 API might tell Constant Contact to use the new editor but this field doesn't seem to be available in the v2 API.
The other problem is that square brackets are now treated as reserved characters by the editor so we've had to scrub our subject and messages of them or we get errors.
Your speculation is correct, the format_type property used when creating an email campaign via our v3 API does control whether the campaign is created in the format used by our legacy custom code editor (format_type 1) or our modern custom code editor (format_type 5). As you noted, users of our website interface are no longer able to edit or schedule campaigns that are in the legacy format; they are only able to copy them into the modern format. This change was initially made last month, but was temporarily rolled back. It was re-implemented a few days ago.
It is still possible to schedule campaigns in the legacy format using the v2 API, however the v2 API does not have the ability to create email campaigns in the modern custom code format. Our development and implementation of newer features is focused on the v3 API, as the current version. If you do need to continue with a mixed workflow (creating campaigns via the API, scheduling via the website), the best solution would be to migrate your integration to the v3 API.
You are also correct that, in the modern custom code editor, square brackets are not supported within the subject line. Square brackets are reserved due their use in Subject Line Personalization, which was not available in the legacy custom code editor. While I'm unable to estimate when or if support for brackets in the subject line could be added, we do have an open feature request, and I've added your account's interest to that request.
Please let us know if you have any questions.
Thank you for confirming that moving to the v3 API is a way forward.
Unfortunately, you've put us in the position of having to do a significant amount of work to stay with Constant Contact.