As part of our platform modernization, we are officially deprecating support for the Marketo Engage SOAP API interface as of October 31, 2025. While SOAP played an important role in early integrations, the REST API has long since become the standard for new development. It’s faster, simpler to work with, and better supported by tools and frameworks across languages.
All new functionality is exclusively available through the REST API. If you’re still using the SOAP API—for example, for lead management, custom object syncing, or program execution—it’s critical to begin migrating now.
Planning Your Migration Strategy
If you're unsure whether your application is using SOAP, check for WSDL references or webService endpoints in your integration code. In many cases, clients built with libraries like Apache Axis or .NET Web Services are tied to SOAP. Once identified, you’ll want to begin translating your integration logic to REST.
For example, SOAP calls for lead operations can often be replaced with endpoints like:
POST /rest/v1/leads.json
Our team has developed a migration toolkit and is available to support customers and partners as they modernize their integrations. Reach out to your Adobe account representative or support contact to get personalized help.
Future-Proofing Your Marketo Integration
These changes are more than just technical housekeeping—they’re about laying a stronger, more secure foundation for the future. With OAuth 2.0 Bearer headers and the REST API as the standard, you can expect better performance, better observability, and enhanced alignment with Adobe’s broader platform strategy.
As always, we’re here to help. If you have questions about your specific implementation or need help migrating legacy code, please don’t hesitate to contact us. You can also visit Adobe Experience League for peer support and guidance.
Thanks for building with us.
.png)
Adchoices