It would be useful for us to enable or or disable an API driven transactional campaign from the UI using a toggle (or checkbox). Currently, if we have to stop sending an email temporarily while we update a template or prep a new template then we have to make a code change that requires a major server deploy.
It would be a lot easier to simply "disable" an email so that even if our server tries to send it using the Maropost API, it will not send. It would also be useful if the Maropost API could return a 4xx error like "{"error": "Campaign ID: 9876 is disabled."}" in this case.
On the campaign list page, I would also add a column or note or color code the disabled campaign differently.
Ideally, you're also tracking when the campaign was last disabled or enabled and maybe have some history logging of the campaign i.e. when it was created, when it was enabled, when it was disabled, when it was enabled again as this will all affect metrics.
