SOAP Web Services Performance Optimization
Oracle NetSuite has scheduled the gradual removal of SOAP web services from the product as part of ongoing efforts to provide modern integration channels.
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.
The support period of older endpoints is also affected and with the 2027.1 release, only the 2025.2 endpoint will be supported. With the 2028.2 release, SOAP will no longer be available in NetSuite and existing SOAP integrations with NetSuite will stop working.
For more details, see the Removal of SOAP Web Services and the SOAP Removal Plans FAQ. For a list of the currently supported endpoints, see Support for Existing WSDL Versions.
SuiteTalk REST web services is the technology intended to replace SOAP. All newly built integrations should use REST web services with OAuth 2.0 for authentication.
-
For any custom integration applications, that you have developed using SOAP, you should start planning the migration of your solution to REST as soon as possible. For a detailed guide for the migration, see SOAP Web Services To Rest Web Services Upgrade Guide.
-
If you use a partner SOAP application to integrate with NetSuite, consult with your partner to provide you with a REST-based application instead.
-
If you use an Oracle NetSuite integration application, a REST-based application will be provided by Oracle NetSuite.
To optimize your SOAP web services, follow these guideline:
-
Use a Web Services Only form to reduce the time it takes to retrieve field values, including sourced and formula fields. For more information, see Forms in SOAP Web Services.
-
Advanced Search allows reference to an existing saved search. For more information, see Reference Existing Saved Searches.
-
Use context API to run minimal user event scripts for real time integration. For more information, see N/runtime Module.
-
Disable SuiteScript and workflow triggers for historical data imports. For more information, see runServerSuiteScriptAndWorkflowTriggers.
-
Use list operations when possible. This approach works with multiple record types, for example, addList Customer then Sales Order. The ideal list size is around 20 transactions, 50 entities or items, and 100 custom records. For more information, see SOAP Web Services List Operations.
-
Use asynchronous operations whenever possible. For more information, see SOAP Web Services Processing.
-
To benefit from increased concurrency, use token-based authentication. For SOAP web services that use token-based authentication (TBA) and for RESTlets, there are no per-user limits for concurrent requests, if the concurrency governance is enabled. For more information, see Web Services and RESTlet Concurrency Governance. This topic also contains a decision chart to help you decide whether you need more SuiteCloud Plus licenses to achieve optimal results.
-
Optimize system notes logging.
-
Disable System Notes for custom fields and for custom record types. (SOAP preference). For more information, see disableSystemNotesForCustomFields.
-
Log System Notes on update only (general preference). For more information, see Setting General Account Preferences.
-
-
You can use Application Performance Management (APM) to monitor and analyze SOAP web services performance. For information, see Analyzing Web Services Performance.