API: Cannot access content for Acrite Email asset - how to create and update email? | Community
Skip to main content
K
Kamyk
Level 1
February 18, 2026
Solved

API: Cannot access content for Acrite Email asset - how to create and update email?

  • February 18, 2026
  • 1 reply
  • 36 views

Hi,

My colleague created a new email template using the new Email Designer tool in Adobe Marketo Engage. I am trying to:

  1. Create an email using this template via REST API

  2. Update the content of that email programmatically

However, I am encountering issues.

Problem 1 – Cannot create email

When I attempt to create an email using:

 

POST /rest/asset/v1/emails.json

I receive the error:

 

Cannot find an approved version of the email template

The template is shown as Published in the UI, so I’m not sure why the API cannot find an approved version.

Problem 2 – Cannot update content

If I manually create the email in the UI using this new template and then try to update its content via API using:

 

POST /rest/asset/v1/email/{emailId}/content.json

I receive the following error:

 

Cannot access content for Acrite Email asset

Questions

  • Are there different REST endpoints for emails/templates created with the new Email Designer?

  • Is content update via /content.json supported for this type of asset?

  • Is the new Email Designer using a different asset model that is not fully supported by the current REST API?

  • Is REST API content manipulation only supported for classic email templates?

The documentation appears to reference the older email template system, which I was previously using without any issues.

I would appreciate clarification on the current API support and limitations for the new Email Designer templates.

Thank you.

    Best answer by Darshil_Shah1

    Emails built with the new Designer don’t use the classic editable-section template model. They’re component/block-based under the hood, while the existing REST endpoints (like /emails.json and /content.json) were built for classic email assets.

     

    That explains both errors:

    Problem 1 – Cannot create email

    “Published” in the new Designer doesn’t always map to the legacy “approved” state the API expects. Creation via API from new Designer templates is not supported.

     

    2. “Cannot access content for Email asset”
    The /email/{id}/content.json endpoint works only for classic emails where sections are API-addressable. New Designer emails don’t expose content that way, so content updates via REST aren’t supported. So yes, Assets being edited via API is not supported in the new Email Designer at this time. The program documentation's FAQ also states the same thing.

    If you want to create/update emails using API, you should consider using the classic emails.

    1 reply

    Darshil_Shah1
    Community Advisor and Adobe Champion
    Darshil_Shah1Community Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    February 18, 2026

    Emails built with the new Designer don’t use the classic editable-section template model. They’re component/block-based under the hood, while the existing REST endpoints (like /emails.json and /content.json) were built for classic email assets.

     

    That explains both errors:

    Problem 1 – Cannot create email

    “Published” in the new Designer doesn’t always map to the legacy “approved” state the API expects. Creation via API from new Designer templates is not supported.

     

    2. “Cannot access content for Email asset”
    The /email/{id}/content.json endpoint works only for classic emails where sections are API-addressable. New Designer emails don’t expose content that way, so content updates via REST aren’t supported. So yes, Assets being edited via API is not supported in the new Email Designer at this time. The program documentation's FAQ also states the same thing.

    If you want to create/update emails using API, you should consider using the classic emails.

      K
      KamykAuthor
      Level 1
      February 18, 2026

      Thanks! I am slightly worry about deprecation:

       

      Will the old email editor continue to function? If so, for how long?

      Yes, the old (classic) email editor will co-exist with the new Email Designer. Emails created in the classic editor will remain. There is no date as to when the classic editor will be deprecated at this time, but it will continue to function into 2026. We will give several months’ notice before we deprecate the old editor.

       

      So what happens next? If we’ve lost the ability to create editable templates via the API, how can I automate email creation?

      SanfordWhiteman
      SanfordWhiteman
      Level 10
      February 18, 2026

      It’s unthinkable (quite literally impossible due to certain dependencies) that Email Editor 2.0 will go away while Email Editor 3.0/Acrite isn’t accessible via API, leaving us with no API access to email assets.

       

      That said, there will certainly be seismic changes to the API to accommodate 3.0 templates/emails, so even if there’s some overlap we need to prepare for rapid learning.

        Terms & ConditionsAccessibility statement

        Loading footer...