Marketo SOAP API
/soap/* version retirement
Stopped workingSubscribe to Marketo SOAP APIShare
On July 31, 2026, the Marketo SOAP API reached deprecation and was shut down. Requests sent to /soap/* fail since that date. The interface is no longer available for any calls.
Calls it hits
/soap/*
What to use instead of these calls
Call the Marketo REST API at {munchkinId}.mktorest.com/rest/v1/... using an access token obtained from /identity/oauth/token. This transition requires more than changing an identifier, as the REST API authenticates using a LaunchPoint custom service's client ID and secret, which SOAP integrations do not have.
The REST API authenticates with a LaunchPoint custom service's client ID and secret, a credential the SOAP integration does not have.
In Marketo SOAP API's words
As of July 31st, 2026,the SOAP API is deprecated and is no longer be available. All new development should be done with the Marketo REST API .
Facts
- API
- Marketo SOAP API
*.mktoapi.com - Kind
- Version retirement
- Takes effect
- July 31, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Marketo SOAP API's own pages
Questions
When does this change take effect?
Calls to /soap/* on Marketo SOAP API stopped working on July 31, 2026.
What happens to calls after July 31, 2026?
They have failed since July 31, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.