Microsoft Advertising Customer Management API
/Api/* version retirement
Stops workingSubscribe to Microsoft Advertising Customer Management APIShare
On January 31, 2027, the Customer Management SOAP API will be fully deprecated and will stop working. Calls to the /Api/* endpoints will fail after this date. Services that rely on the SOAP interface must transition before the retirement takes effect.
Calls it hits
/Api/*
What to use instead of these calls
Call the Customer Management and Customer Billing REST APIs instead. Alternatively, upgrade the .NET or Java SDK to version 13.0.22 or later, or migrate from the Python or PHP bingads package to msads.
In Microsoft Advertising Customer Management API's words
The SOAP API is scheduled for full deprecation on January 31, 2027. We recommend migrating to REST as soon as possible to ensure a smooth transition and avoid disruption when SOAP is deprecated.
Facts
- API
- Microsoft Advertising Customer Management API
clientcenter.api.bingads.microsoft.com - Kind
- Version retirement
- Takes effect
- January 31, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Microsoft Advertising Customer Management API's own pages
Questions
When does this change take effect?
Calls to /Api/* on Microsoft Advertising Customer Management API stop working on January 31, 2027.
What happens to calls after January 31, 2027?
They fail from that day.
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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before January 31, 2027.