SOAP Web Services End-of-Life: Full Removal Timeline and Migration Path to REST

What changed

Oracle has formalized the SOAP web services removal timeline. The key milestones are:

• 2025.2 — Last planned SOAP WSDL endpoint. No new endpoints will be issued unless Oracle deems it necessary for business or technical reasons.
• 2026.1 — All new integrations should use SuiteTalk REST with OAuth 2.0. SOAP is still functional but discouraged for new work.
• 2027.1 — New Integration Records using Token Based Authentication (TBA) can no longer be created. Because SOAP requires TBA, this effectively blocks creation of new SOAP integrations. Existing Integration Records for SOAP/TBA may still be modified.
• 2027.2 — Only the 2025.2 endpoint remains supported (bug fixes). All older endpoints drop to unsupported-but-available status.
• 2028.1 — Oldest unsupported endpoints continue to be disabled each release.
• 2028.2 — All SOAP endpoints are disabled. SOAP-based integrations stop working entirely.

Endpoint support matrix

Each release disables the oldest unsupported endpoint. The statuses are: S = Supported, U = Available without support, - = Disabled.

• 2025.2 endpoint — Supported through 2028.1, disabled at 2028.2.
• 2025.1 / 2024.2 — Supported through 2027.1, then unsupported-but-available until 2028.2.
• 2024.1 — Supported through 2026.2, unsupported from 2027.1, disabled at 2028.2.
• 2023.2 — Supported through 2026.1, unsupported from 2026.2.
• 2023.1 and older — Already unsupported. Progressively disabled each release. Endpoints 2021.1 and older begin going dark at 2028.1 or earlier.
• 2019.1 and 2018.2 — Already disabled or disabled at 2026.1.

Authentication impact

SOAP relies on Token Based Authentication (TBA). Starting with 2027.1, TBA is blocked for new Integration Records. If you have REST-based integrations currently using TBA, Oracle recommends migrating to OAuth 2.0 but does not require it until the 2027.1 cutoff for new records. Existing TBA-based REST integrations continue to function, but the direction is clear: OAuth 2.0 is the only authentication method going forward.

REST parity gaps

Oracle acknowledges that 100% REST parity with SOAP is not planned. Some legacy SOAP functionality — including certain operations and record types — will not be exposed in the REST API. The official guidance for anything unavailable in REST is to use SuiteScript RESTlets as a bridge. Specific gaps to be aware of:

• Legacy tax — Legacy tax support in REST is planned for upcoming releases, but Oracle explicitly recommends migrating to SuiteTax instead of waiting.
• Record types and fields — New records have not been added to SOAP for several years. REST is the only API receiving new record coverage.
• SuiteAnalytics Workbooks and SuiteScript 2.x Analytics APIs — Not available via SOAP at all; only accessible through REST or SuiteScript.

Oracle publishes a SOAP Web Services To REST Web Services Upgrade Guide that maps each SOAP operation to its REST equivalent. This guide is updated each release as parity improves. Refer to it for operation-by-operation migration details.

What to do

1. Audit your integration records now. In NetSuite, go to Setup > Integration > Manage Integrations and identify every record using SOAP or TBA. Flag any that are still actively used.
2. Stop building on SOAP. Any new integration work should target the SuiteTalk REST API (/services/rest/record/v1/) with OAuth 2.0 client credentials or authorization code flow.
3. Plan REST migration for existing SOAP integrations. Use the official upgrade guide to map your SOAP get, getList, search, add, update, upsert, and delete calls to their REST equivalents (GET, POST, PATCH, PUT, DELETE on /services/rest/record/v1/{recordType}/{id}).
4. Identify parity gaps early. Test your critical record types and operations against the REST API. Where REST coverage is missing, build SuiteScript 2.x RESTlets (N/https, N/record, N/search, or N/query) to fill the gap.
5. Migrate authentication. Switch existing TBA integrations to OAuth 2.0. For machine-to-machine flows, use the OAuth 2.0 Client Credentials grant (Certificate or Client Secret). For user-context flows, use the Authorization Code grant with PKCE.
6. If you rely on legacy tax through SOAP, begin evaluating SuiteTax. Waiting for legacy tax REST support is risky given the 2028.2 hard cutoff.
7. Contact third-party vendors. If you use partner-built SuiteApps or connectors that depend on SOAP, confirm their REST migration timeline. Do not assume they will be ready before 2028.2.
8. Pin your current SOAP endpoint. If you must continue using SOAP during migration, ensure you are on the 2025.2 endpoint — it is the only one guaranteed supported through 2028.1.

Key dates summary

• Now — Start all new integrations on REST + OAuth 2.0.
• 2027.1 — Hard block on new SOAP/TBA Integration Records.
• 2028.2 — All SOAP endpoints disabled. Zero SOAP traffic will be processed.