Microsoft Advertising API
/Api/* version retirement
Stops workingSubscribe to Microsoft Advertising APIShare
On January 31, 2027, the Campaign Management SOAP API will undergo full deprecation. Requests made to /Api/* endpoints will fail after this date. Services and applications relying on these endpoints must update their integration to prevent disruption.
Calls it hits
/Api/*
What to use instead of these calls
Call the Campaign Management REST API instead, or upgrade the .NET or Java SDK to version 13.0.22 or later. Developers using Python or PHP should migrate from the bingads package to msads.
In Microsoft Advertising 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 API
campaign.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 API's own pages
Questions
When does this change take effect?
Calls to /Api/* on Microsoft Advertising 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.