Microsoft Advertising Bulk API
/Api/* version retirement
Stops workingSubscribe to Microsoft Advertising Bulk APIShare
On January 31, 2027, the Bulk SOAP API stops working. Calls to endpoints matching /Api/* will fail after this date because the SOAP API undergoes full deprecation.
Calls it hits
/Api/*
What to use instead of these calls
Migrate by calling the Bulk REST API instead. Alternatively, upgrade the .NET or Java SDK to version 13.0.22 or later, or switch from the Python or PHP bingads package to msads.
In Microsoft Advertising Bulk 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 Bulk API
bulk.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 Bulk API's own pages
Questions
When does this change take effect?
Calls to /Api/* on Microsoft Advertising Bulk 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.