Oracle NetSuite is changing its SOAP Web Services endpoint release and support policy

Oracle Community: SOAP Web Services endpoint release and support policy changes 

• Starting with the 2026.1 release, new SOAP Web Services endpoints will no longer be published automatically with each release. Each SOAP endpoint is supported for three years from its initial release date.

Immediate Impact on Integrations!! 

Each SOAP Web Services endpoint is supported for three years from its release. With every new NetSuite release, the oldest version is retired, making its WSDL unavailable and breaking any dependent integrations.

• Three-Year Support Window: Each SOAP version you use is supported for three years from its release. For example, 2023.x endpoints will expire in 2026, whereas the 2022.1 endpoint, which was launched in 2022, has been made unsupported in 2025.

• Prioritize At Risk Versions: Review your integrations and focus first on any that use SOAP API versions already unsupported or nearing their three year mark (for example, 2023.x and earlier).  

Old Policy vs New Policy: What’s Changed? 

Previously, NetSuite’s SOAP policy followed a “sixversion” rule: at any time, the six most recently released WSDL endpoints were supported. Under the new policy, each SOAP endpoint is supported strictly for three years from its release date—regardless of how many platform versions occur in that period—and new endpoints will no longer be published automatically with each upgrade. 

Identify If Your System is Impacted: 

There are two ways to determine whether your system is using a SOAP Web Services version that is unsupported or nearing retirement:

1. Using Application Performance Management (APM) tool 

If your NetSuite account has APM, you can use it to monitor SOAP Web Services usage by version: 

A. Navigate to: Customization > Performance > SOAP Web Services Analysis

B. Scroll to the section titled: SOAP Web Services API Version Usage

This portlet displays the total number of SOAP requests made using each API version. If you see calls to older versions (such as 2023.x or earlier), these integrations may be impacted and require updates. 

Focus on these categories: 

If APM is not currently installed in your account, you can review the following instruction for installing it: Installing the Application Performance Management SuiteApp 

2. Using a Saved Search 

If APM is unavailable or if you want a more detailed breakdown, you can use a Saved Search on SOAP Web Services operations: 

1. Navigate to: Reports > Saved Searches > All Saved Searches > New

2. Select: SOAP Web Services Operations

3. Under Criteria, add: 

• Add Api Version to filter. 

• Select all version expect the 9999_9 and 2025_1

4. Under Results, include:

This search will show you all SOAP calls by integration and API version—so you can immediately see which integrations still run on versions that are expiring or already expired:

Action for Popular Integration Tools 

Once you know which integrations use SOAP, you can take targeted action. At GIR we’ve already helped clients with all major integration platforms. For example: 

• Dell Boomi

• Celigo

• ShipHawk 

Why You Must Act Now 

This change is critical because once a SOAP endpoint reaches end-of-life, your integrations will silently break. The endpoint will stop getting fixes and eventually reject calls. 

Moving sooner gives you breathing room. We strongly recommend upgrading to the 2025.2 SOAP endpoint as soon as it’s available – this extends support until at least 2028.2. Even better, redesign integrations to use NetSuite’s REST Web Services, which NetSuite now prefers for future-proof security. 

Need help? GIR is here to guide you through this transition. Call us at  (713) 570-0483 or email info@girsoftwareservices.com to schedule a review of your SOAP footprint. Don’t wait until your integrations fail – let us help you ensure a smooth, disruption-free migration away from deprecated SOAP APIs.