SOAP Web Services: 2026.1 Deprecation Schedule Locked
Oracle has published the formal sunset timeline for SOAP/SuiteTalk WSDL endpoints. New accounts can no longer enable SOAP, and existing accounts have a defined runway before WSDL versions begin to be retired.
The 2026.1 release notes formalize what has been signaled for years: SOAP-based SuiteTalk is on a deprecation clock. New provisioned accounts no longer get the feature toggle, and the oldest WSDL versions enter retirement starting with this release.
Why this is a code-level concern
SOAP integrations encode the WSDL version at compile time — a retired WSDL means a recompile, not just a config change. Java and .NET stubs generated against WSDL 2018.x and earlier will start failing handshake when their endpoint is retired.
Migration order of operations
- Inventory every SOAP integration. Saved searches under Setup > Integration > Web Services Usage Log broken down by user and WSDL version are the fastest way.
- Identify which records and operations each integration touches. Cross-reference against the REST Record Service supported list — most common transaction types are now covered.
- Re-platform on REST Record Service or, where REST is still insufficient, RESTlets. Treat SuiteScript-backed RESTlets as the escape hatch, not the destination.
- Switch authentication from TBA to OAuth 2.0 as part of the migration — do not carry TBA forward into new code.
We covered the strategic angle in our blog post on NetSuite Sunsetting SOAP; the 2026.1 notes are the first time the actual dates are in writing.
Source: Oracle NetSuite Release Notes