SOAP Removal Plans FAQ
This page answers frequently asked questions about the SOAP removal initiative, the SOAP web services life cycle, and end of support of the SOAP endpoints.
General Questions
Why is Oracle NetSuite removing SOAP web services?
Oracle NetSuite wants to provide modern integration channels and SOAP no longer meets the set standards:
-
Exposed objects – SOAP does not support the latest business features and new records have not been made available to SOAP for a couple of years.
-
Outdated Technology Stack – SOAP does not support modern architecture standards like the most up-to-date metadata architecture, SuiteAnalytics Workbooks, and SuiteScript 2.x Analytics APIs.
-
Legacy Authentication – SOAP still uses token-based authentication, which is not consistent with other Oracle products and does not meet modern security standards.
What is replacing SOAP web services?
SuiteTalk REST web services is the technology intended to replace SOAP.
-
Most functional use cases implemented using SOAP can already be implemented using REST web services.
-
Significant investments have been made in the REST API to achieve functional parity with SOAP, and there are plans to fill any remaining gaps in upcoming releases.
-
For specific scenarios where REST web services cannot be used, it is possible to use SuiteScript RESTlets.
Can I still build new integrations using SOAP web services?
Starting with the 2026.1 NetSuite release, all newly built integrations should use REST web services with OAuth 2.0. With the 2027.1 release, you will not be able to build any new integrations using SOAP web services.
I have a REST-based integration which uses Token Based Authentication (TBA). Should I migrate it to OAuth 2.0 authentication?
Although OAuth 2.0 is the preferred authentication method, and you should consider changing the authentication method of your existing REST-based integration that uses TBA, only new integrations must use OAuth 2.0, starting with the 2027.1 NetSuite release.
Since 2025.2 is the last planned endpoint, should I start planning the transition of my integrations to REST web services now?
Yes, when you build new integrations, use REST web services and the OAuth 2.0 authentication method. Also, consider transitioning your existing SOAP integrations to REST web services and the OAuth 2.0 authentication method. REST web services is the integration channel you should use, and it meets the latest industry requirements. For specific scenarios where REST web services cannot be used, it is possible to use SuiteScript RESTlets instead.
I use a SOAP-based application developed by NetSuite. What should I do?
NetSuite will provide an alternative REST-based application in time.
I use a SOAP-based application provided by a partner. What should I do?
Contact your partner and discuss a timeline for the provision of an alternative REST-based application instead.
Do you have a guide to help me with the development of an alternative REST-based application?
A SOAP Web Services To Rest Web Services Upgrade Guide for the transition from SOAP to REST web services is available. The guide is updated with additional enhancements as greater parity of REST with SOAP web services is achieved, so make sure you have the latest version.
Removal Timeline Questions
Has a specific date been set after which it will no longer be possible to create new integrations using SOAP web services?
Starting with the 2026.1 NetSuite release, you should build any new integrations using REST web services. With the 2027.1 NetSuite release, it will no longer be possible to build new integrations using SOAP web services.
I use the 2025.1 SOAP endpoint. Will this endpoint be supported for 3 years?
Starting with the 2027.2 NetSuite release, only the last endpoint will be supported and have any potential bugs fixed. Older endpoints will still be available, but no longer supported, until the final removal of SOAP web services with the 2028.2 NetSuite release.
The 2025.2 SOAP endpoint is the last planned SOAP endpoint and any later SOAP endpoints would be released only as necessary to meet business, technical, or other significant requirements.
How long will the unsupported endpoints still be available?
With every NetSuite release the oldest unsupported endpoint is disabled. With the 2028.2 NetSuite release, all endpoints will be disabled, and SOAP-based integrations will stop working.
Until when will each endpoint be available or supported?
The following table shows the endpoint version and its status with every NetSuite release:
S: Supported endpoint
U: Available endpoint without support
" – ": Disabled, unavailable endpoint
|
Endpoint Version/NetSuite Release |
2025.2 |
2026.1 |
2026.2 |
2027.1 |
2027.2 |
2028.1 |
2028.2 |
|---|---|---|---|---|---|---|---|
|
2025.2 |
S |
S |
S |
S |
S |
S |
– |
|
2025.1 |
S |
S |
S |
S |
U |
U |
– |
|
2024.2 |
S |
S |
S |
S |
U |
U |
– |
|
2024.1 |
S |
S |
S |
U |
U |
U |
– |
|
2023.2 |
S |
S |
U |
U |
U |
U |
– |
|
2023.1 |
S |
U |
U |
U |
U |
U |
– |
|
2022.2 |
U |
U |
U |
U |
U |
U |
– |
|
2022.1 |
U |
U |
U |
U |
U |
U |
– |
|
2021.2 |
U |
U |
U |
U |
U |
U |
– |
|
2021.1 |
U |
U |
U |
U |
U |
– |
– |
|
2020.2 |
U |
U |
U |
U |
– |
– |
– |
|
2020.1 |
U |
U |
U |
– |
– |
– |
– |
|
2019.2 |
U |
U |
– |
– |
– |
– |
– |
|
2019.1 |
U |
– |
– |
– |
– |
– |
– |
|
2018.2 |
– |
– |
– |
– |
– |
– |
– |
The 2025.2 SOAP endpoint is the last planned SOAP endpoint and any later SOAP endpoints would be released only as necessary to meet business, technical, or other significant requirements.
SOAP vs REST Parity And Enhancement Questions
When should we expect REST to achieve parity with SOAP web services in terms of capabilities, record types, and fields? Could the lack of feature parity potentially hinder our transition to REST web services?
Oracle NetSuite is investing heavily into achieving REST parity with SOAP. Most existing SOAP solutions can already be migrated to REST, and parity will be significantly improved in the upcoming NetSuite releases. You should not expect 100% parity of REST with SOAP, because some legacy functionalities in SOAP should not be used any longer and will not be exposed in REST web services. When an object or method is not available in REST web services, you should use SuiteScript RESTlets instead.
I use a specific SOAP operation. How can I achieve the same result in REST?
The SOAP Web Services To Rest Web Services Upgrade Guide provides details, such as alternatives for each SOAP operation. The guide will be updated in the next release with the latest added features.
When will legacy tax support be available in REST?
Although legacy tax support is planned for the upcoming product releases, you should consider using SuiteTax instead.
Can you share a roadmap with the additional enhancements and their expected delivery?
The parity level of REST with SOAP web services is indicated in the upgrade guide, and there are plans to fill any remaining gaps in upcoming releases. You should not expect 100% parity of REST with SOAP, because some legacy functionalities in SOAP should not be used any longer and will not be exposed in REST web services. When an object or method is not available in REST web services, you should use SuiteScript RESTlets instead. To keep up with additional enhancements and their delivery make sure you read the latest SOAP Web Services To Rest Web Services Upgrade Guide, and watch the release notes of upcoming releases.