You can now create and manage email series and transactional campaigns via the Quanda API, just like a simple email campaign. A developer connects them directly to a CRM, ERP, DMS or your own application. A marketer then keeps editing them in the app as before.
Key takeaways
- You create an email series (campaign type 30) or a transactional campaign (type 70) in one call, which creates the campaign and its first email.
- Via the API, you change the settings, manage the emails, send a test and activate, pause and resume the campaign.
- You start a series with the activation call with a start date on the full hour and a period of 1 to 60 days.
- The test goes to no more than 3 addresses and the HTML must contain the
{{ unsubscribe_link }}tag.- You can edit a running campaign only after pausing it, and the same checks run before activation as in the app.
In brief: what is new, since when, who it concerns and where to find it
- What is new: besides the simple campaign, the API now handles two more campaign types, the email series and the transactional campaign.
- Since when: since 20 November 2026.
- Who it concerns: developers and integrators who connect Quanda to a CRM, ERP, DMS or their own application, and marketers who use series and transactional emails.
- What is not included: birthday, anniversary, logic and A/B campaigns and the setup of automations.
- Where to find it: in the API documentation in the Email series and Transactional emails sections.

What's new in the API for email series and transactional emails
The Quanda API can now create and manage an email series and a transactional campaign. Until now, the API let you create, edit, test and send only a simple email campaign. Series and transactional emails could only be created in the app.
An API is an interface through which two systems exchange data without manual clicking. An email series, sometimes called an email sequence or drip campaign, is a set of emails that contacts with selected tags receive one by one at an interval of a set number of days. You prepare a transactional email in Quanda in advance, and it goes out at the moment a contact meets a condition, for example after an order.
What you can now do via the API:
- Creation in one call. A call is a single request from your system to the API. It creates the campaign and its first email, just as with a simple campaign.
- Management of both campaign types. You change the campaign settings, add, edit and delete an email and read the list of emails. You send a test email and activate, pause and resume the campaign.
- Series settings. The contact tags the series is sent to, the period between parts from 1 to 60 days, the start date and hour and the order of the parts. On top of that, the state of a part and the tags that are added to or removed from the contact after the part is sent.
- Test email of a series. You choose all parts, only parts edited today or selected parts, just like in the app. The test goes to no more than 3 addresses.
- Email content. You send it as HTML or have it created from a template.
- Availability. The API is included in all plans of the Custom package, and in the Professional and Enterprise plans of the Emails only option, see the pricing page.
- Working with an AI assistant. Email series and transactional campaigns can also be created and managed by an AI assistant connected via the Quanda MCP server.
Other ways to connect, including ready-made connections without programming, are summarized in the guide Connect Quanda with your website, CRM or other software holding your contacts.
What to use email series and transactional emails via the API for
The API pays off wherever campaigns are created or change based on data from another system. Nobody then has to create the campaign or rewrite it manually in the app. Three typical situations:
A welcome series created from a CRM. The CRM creates a welcome series for new customers itself. One call creates the campaign with the first part, further calls add more parts. It sets the new customers tag, the period and the start. A marketer then checks the series in the app and activates it. What else series can do in Quanda is shown on the Email marketing page.
A transactional email managed from your own system. When the text of a transactional email changes, for example an order confirmation, your system edits it via the API and sends itself a test. How to prepare a transactional email in the app is described in the guide Transactional emails for automations.
Bulk editing of series parts. You need to change the footer or a link in all parts. A script reads the list of emails, edits each part and sets its state to To check. A colleague then goes through them in the app and marks them as Checked.
How to create an email series via the API
You create and start a series via the API in six steps. Each step is one or more calls, and you send every call with the API key in the header. The series stays in the Under construction state and sends nothing until you activate it.
- Create the series. With the
POST /api/newsletter/campaigns/30/call, send the campaign name, the manager, the sender, the language, the subject and the content of the first part as HTML or from a template. This creates the campaign and its first part. - Add further parts. You add each part with a separate call and change their order as needed.
- Set the recipients. Enter the contact tags the series is sent to. Optionally, add the tags that are added to or removed from the contact after a part is sent.
- Mark the state of the parts. Each part has the state Draft, To check, Checked or Done.
- Send a test email. Choose all parts, only parts edited today or selected parts. The test goes to no more than 3 addresses.
- Activate the series. With the
POST /api/newsletter/campaigns/{campaign_id}/activate/call, send the start date and hour and a period of 1 to 60 days. The start must be today or later and on the full hour. Before activation, the same checks run as in the app: a verified sender email and domain, valid content and a spam check.
This is what the activation call looks like that starts the series on 1 December 2026 at 9:00 with a period of 3 days:
POST https://api.onquanda.com/api/newsletter/campaigns/{campaign_id}/activate/
content-type: application/json
authorization: Token YOUR_API_KEY
{"start_at": "2026-12-01T09:00:00", "period": 3}
You create a transactional campaign with the POST /api/newsletter/campaigns/70/ call and then manage it with calls similar to those for a series. A series created via the API is a regular campaign, and you can keep editing it in the app. This also works the other way round.

What to watch for when editing via the API
The same safety rules apply to series and transactional campaigns via the API as in the app. Watch these five in particular.
- Pause the campaign before editing. A running campaign cannot be edited. First pause it, edit it and then resume it, just as in the app.
- Unsubscribe link. The email HTML must contain the
{{ unsubscribe_link }}tag. The tag is placeholder text that Quanda replaces with the unsubscribe link when sending. - A new date after a missed dispatch. If the date of the next dispatch of a paused series passes in the meantime, you enter a new start date and period when you resume it, using the activation call. The same in the app is described in the guide Setting up mailing of an email series.
- Send requests one at a time. Send requests with one API key one after another, not in parallel. There is a 30 ms delay between the end of one request and the start of the next, and if you access the API too often, it returns code 429 and the request has to be repeated. Keep this in mind especially in a script that edits all parts of a series at once.
- A new version of the email. When you change the links in an email of a running campaign that has already been sent, a new version of the email is created. The statistics of the sent version are kept.

What stays the same in the API
The new release only adds new calls, and existing integrations keep working without change. Specifically:
- The API for simple campaigns works without change.
- The endpoints, that is the addresses your system sends calls to, stay the same.
- Sending transactional emails to individual recipients via the API works as before.
- The app behaves the same as before.
Birthday, anniversary, logic and A/B campaigns are not part of this release. You also cannot set up automations via the API.
Email series and transactional emails via the API: summary
You can now create and manage series and transactional campaigns via the API, just like a simple campaign and with the same rules as in the app. All calls, fields and error responses are described in the API documentation in the Email series and Transactional emails sections. How to get an API key is explained in the help article API documentation and API key. The series settings in the app are described in the guide How to create and set up an email series.
Our support team is happy to help you with the connection at support@onquanda.com or on +420 605 163 892.
The Quanda team