Adobe Marketo Engage February 2026 release adds Email Designer API and image models
Adobe's February 2026 Marketo Engage release, starting February 20, 2026, adds API access to the Email Designer, folder actions, and Nano Banana image generation in the AI Assistant alongside Firefly.
Adobe published release notes for the February 2026 Marketo Engage release, with standard release cycle features starting to roll out on February 20, 2026. All three listed features apply to the Email Designer and are marked released. The announcements section introduces a cap on the REST API Merge Leads call and restates the SEO feature deprecation, the August 31, 2026 end date for the access_token parameter and the July 31, 2026 end of SOAP API support.
The details
- Email Designer assets can now be managed through API calls documented in the Marketo Asset API.
- The AI Assistant can generate email images with Nano Banana models as well as Firefly.
- Folder actions add share, archive, cross-workspace sharing and drag-and-drop moves for Email Designer assets.
- From July 31, 2026, Merge Leads calls with more than 25 IDs return a 1080 error code and are skipped.
Context
The February release follows the January 2026 release, which added AI Assistant brand asset prompting and Email Designer folders. Our coverage of Marketo Engage since October 2025 has otherwise covered Dynamic Chat changes in March 2026 and the November 2026 release that lists Callable Agents. The Merge Leads limit announced here is repeated in later release notes through August 2026.
Not disclosed
- Whether Nano Banana image generation carries additional cost or credit use
- Rate limits for the Email Designer API
- Edition availability for each feature
- Vendor
Adobe Marketo Engage- Category
- CRM & Marketing Automation
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.




