Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Microsoft Advertising is transitioning from the legacy SOAP API to the REST API.
Based on customer feedback, we’ve updated our transition approach to provide additional flexibility. SOAP integrations will continue to be supported, including access to API features and enhancements, through January 31, 2027.
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. SDK and non-SDK migration guides are available below.
.NET SDK
If you are using a version of BingAds .NET SDK lower than 13.0.22, please Upgrade to latest Bing Ads .NET SDK.
Java SDK
If you are using a version of BingAds Java SDK lower than 13.0.22, please Upgrade to latest Bing Ads Java SDK.
Python SDK
If you are using any version of the bingads package, please Upgrade to new msads package.
PHP SDK
If you are using any version of the bingads package, please Upgrade to new msads package.
No SDK
If you are accessing SOAP API directly without using an SDK, please update your code to call the API using REST API URLs and request format. Please use the API reference documentation to find REST API URLs and request examples for each API method used by your code.
Microsoft Advertising API transition: SOAP to REST
Microsoft Advertising is transitioning its API platform from SOAP to REST to provide a more modern and efficient integration experience.
What’s changing
- REST APIs are becoming the standard foundation for all future Microsoft Advertising API development.
- Existing SOAP integrations will continue to be supported, including access to API features and enhancements, through January 31, 2027.
- The SOAP API is scheduled for full deprecation on January 31, 2027.
Why move to the REST API
- Ongoing access to new API features and capabilities
- Strong SDK support
- Modern HTTP/JSON architecture
- Simplified integration and debugging
- Broad programming language support
- Smaller payloads with HTTP compression, reducing latency and traffic
How to get started
- SDK users: Follow the SDK migration guides above to transition from SOAP to REST.
- Non‑SDK users: Update integrations to use REST endpoints and request formats in the API reference documentation.
- If you’re not currently using an SDK, migrating is a good opportunity to adopt one to simplify future updates.