Marketo API becoming obsolete: New Endpoints needed to programatically Create/Edit Smart Campaigns (flows and filters) AND Smart Lists

Summary of Request The current Adobe Marketo Engage REST API is severely limited regarding the programmatic construction of marketing assets. While we can "Clone" or "Trigger" assets, we completely lack the ability to Create, Read, Update, and Delete (CRUD) the internal logic of Smart Campaigns (Flow Steps & Triggers) and Smart Lists (Filters & Rules) via API.

As marketing operations move toward hyper-automation and dynamic campaign generation, the inability to define campaign logic via code is rendering the Marketo API obsolete compared to modern, developer-friendly platforms. We urgently request new endpoints to manipulate these assets' definitions directly.

Current Limitations & Pain Points

1. Smart Campaigns are "Black Boxes" to the API:

   • The Problem: We can create a shell campaign or clone an existing one, but we cannot add, edit, or order Flow Steps (e.g., "Send Email," "Change Data Value," "Wait") or Smart List Triggers via API.

   • The Impact: We cannot dynamically generate campaigns based on external data signals. If we have 100 micro-segments requiring slightly different flow logic, a human must manually build 100 campaigns in the UI. This prevents true scale and automated campaign execution.

2. Smart Lists cannot be defined programmatically:

   • The Problem: The Asset API allows us to clone a Smart List, but not to inject or modify its Filters (e.g., "Industry is X" AND "Score > 50").

   • The Impact: We cannot automate audience segmentation. External systems (like a custom CDP or data warehouse) cannot push segmentation logic into Marketo. We are forced to use static lists (which don't update in real-time) or manual UI work.

3. Inefficient Workarounds:

   • Current workarounds involve cloning "Template Programs" and using token variables. This is brittle, creates technical debt (thousands of unused clones), and does not solve the need for structural changes to campaign flows (e.g., adding an extra "Wait" step dynamically).

Proposed Solution / Feature Request We request the addition of the following capabilities to the Asset API:

• POST /rest/asset/v1/smartCampaign/{id}/flow: Ability to pass a JSON array defining flow steps (Action, Choice Steps, Constraints, Parameters).

• POST /rest/asset/v1/smartCampaign/{id}/smartList: Ability to define triggers and filters for the campaign's audience.

• POST /rest/asset/v1/smartList/{id}/rules: Ability to add/update filter rules for standalone Smart Lists.

• GET endpoints for the above to retrieve the current logic structure (JSON representation of the Flow/Rules).

Business Justification Modern marketing requires agility. We are building internal tools to orchestrate customer journeys across multiple channels. Without these endpoints, Marketo acts as a bottleneck rather than an engine. Opening these endpoints will allow developers to build powerful automations on top of Marketo, significantly increasing platform stickiness and utilization.

Priority: Critical (Blocking scalable automation initiatives)