How to send email proof/sample via API if created with new designer? | Community
Skip to main content
K
Kamyk
Level 2
March 5, 2026
Question

How to send email proof/sample via API if created with new designer?

  • March 5, 2026
  • 1 reply
  • 14 views

First of all,

The endpoint /rest/asset/v1/emails.json does not return the subject value when the email uses a template created in the new designer.

Additionally, I am unable to send a sample email using /rest/asset/v1/email/{email_id}/sendSample.json. The request returns the following error:

'errors': [{'code': '709', 'message': 'One or more email headers (displayName, fromEmail, replyToEmail, subject) is empty'}]

I do not have this issue when sending emails that were created using the old designer.

 

Is there a way to send a sample email if the email was created using the new designer?

1 reply

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 5, 2026

Hi ​@Kamyk 

No – right now you cannot send a sample via the public REST API for emails created with the new Email Designer.

What you’re seeing is expected given the current product state:

  • Emails built in the new Email Designer are stored as new “content authoring” assets (with different header storage).
  • The classic REST endpoints
    • GET /rest/asset/v1/emails.json and POST /rest/asset/v1/email/{id}/sendSample.json are wired only for legacy/old‑editor emails. For new‑designer emails, header fields (subject, fromEmail, etc.) are effectively empty from the point of view of these APIs, so sendSample fails with:
      • 709 One or more email headers (displayName, fromEmail, replyToEmail, subject) is empty
    • That’s why /emails.json doesn’t show subject for those assets and why sendSample works fine for old‑editor emails but not for new‑designer ones. This is a limitation, not something you can fix in your request.

What you can do today

REST sendSample API: works only with classic/old‑editor email assets until API parity is delivered.
 

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
    K
    KamykAuthor
    Level 2
    March 6, 2026

    Thanks for the clarification.

    Is there any official documentation that clearly states which REST API endpoints are compatible with the new Email Designer and which ones only work with classic/old-editor emails? At the moment it’s a bit difficult to tell whether an endpoint should work, partially work, or is simply not supported for the new designer assets.

    For example, as you mentioned, endpoints like
    GET /rest/asset/v1/emails.json and
    POST /rest/asset/v1/email/{emailId}/sendSample.json

    don’t seem to fully support emails created in the new Email Designer because the header fields (subject, fromEmail, etc.) are not returned the same way.

    Also, just as a note for anyone who might run into the same issue:
    the endpoint

    /rest/asset/v1/email/{emailId}/fullContent.json

    works for both the new Email Designer and the classic editor. It returns the full HTML content of the email, so as a workaround you can fetch the HTML and send it yourself instead of relying on /rest/asset/v1/email/{emailId}/sendSample.json.

    Just wanted to check if there’s any documentation or roadmap notes about API parity between the classic email assets and the new Email Designer.

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    March 6, 2026

    Hi ​@Kamyk 

    There isn't currently any public, official matrix that says which REST email-asset endpoints fully support the new Email Designer vs. only the classic/Email 2.0 editor. The published Email Asset REST docs and the "Email 2.0 and Email API FAQ's" were written for the classic email model and don't call out the new designer explicitly, which is why /rest/asset/v1/emails.json and /rest/asset/v1/email/{id}/sendSample.json behave as if the headers are "missing" for new-designer emails.

    Right now:

    • sendSample.json is effectively supported only for classic/old-editor email assets (new designer emails typically fail with 709 because their headers live in the new content-authoring model).
    • fullContent.json is a valid workaround for both classic and new designer (exactly as you described): pull the HTML and send it yourself outside of Marketo.

    Marketo is in the process of adding proper API support for the new Email Designer (see the "Email Designer – API" item in the current release notes, with documentation marked as "coming soon"), but as of today there's no public compatibility/parity guide. If you need this for planning, it's worth logging a Support ticket and an Idea specifically asking for an official endpoint-support matrix for new Email Designer assets.

    https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-28376

    https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/email-marketing/email-designer/overview

    https://experienceleague.adobe.com/en/docs/marketo/using/release-notes/current

    Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
    Terms & ConditionsAccessibility statement

    Loading footer...