An integration scenario for Customer Insights – Journeys (CIJ) where email content is authored externally (e.g., third-party CMS or email design tools), and then programmatically created in Dataverse using the standard Web API endpoint:

POST /api/data/v9.2/msdynmkt_emails

Above operations successfully creates the email record in draft state within CIJ.

CIJ - PG team, request you to please consider this in your future roadmap. At present, lack of documentation for API's appears to create a gap for customers attempting to implement fully automated content pipelines using external systems.

1. Is there a supported and documented API (or action) to transition an email from Draft to a "Ready to Send / Published" state programmatically?

2. We do not see any corresponding actions in the Dataverse metadata or Microsoft Learn documentation that enable publishing or activating the email via API.

3. Based on observed behavior, it appears that CIJ performs additional internal processing steps (e.g., validation, rendering checks, dependency resolution, compliance checks) before an email is considered ready for sending.

4. Is the publishing process dependent on internal CIJ services or orchestration that are not currently exposed via public APIs (similar to what is observed with content blocks)?

5. If so, is this limitation by design, and is there a recommended or supported pattern for:

  - Fully automated email creation + activation workflows

  - Integrating externally authored HTML/content into CIJ while maintaining a supported send process

6. Are there any roadmap considerations or upcoming API enhancements to support this end-to-end automation scenario?

At present, this appears to create a gap for customers attempting to implement fully automated content pipelines using external systems.