SOAP Web Services Governance Overview
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.
NetSuite uses mechanisms to optimize and control SOAP web services usage on its application and database servers. These mechanisms provide the following benefits:
-
Requests are monitored and controlled to prevent excessive impact on the user experience.
-
Heavy SOAP web services usage by some users does not affect other users.
NetSuite SOAP web services governance includes:
-
Record limiting (see Understanding Record Limiting)
-
Request limiting (see Understanding Request Limiting)
For information about the maximum number of sessions, see Session Limits.
For information about the new web services and RESTlet concurrency governance, see Web Services and RESTlet Concurrency Governance.
Understanding Record Limiting
The following limits apply:
-
The number of records in a list operation.
-
The number of records in a page of search results. Search results are set by the pageSize field of the searchPreferences complex type. A minimum and maximum exists for this parameter.
Limits differ for synchronous and asynchronous operations.
Synchronous Operations
|
Minimum Record Count |
Maximum Record Count |
|---|---|---|
|
— |
200 |
|
|
— |
200 |
|
|
— |
1000 |
|
|
— |
10000 |
|
|
— |
100 |
|
|
— |
100 |
|
|
pageSize parameter of searchPreferences complex type, when used in synchronous searches |
5 |
1000 |
Asynchronous Operations
|
Minimum Record Count |
Record Count |
|---|---|---|
|
asyncAddList |
— |
400 |
|
asyncGetList |
— |
2000 |
|
asyncUpdateList |
— |
200 |
|
asyncUpsertList |
— |
200 |
|
asyncDeleteList |
— |
400 |
|
pageSize parameter of searchPreferences complex type, when used in asynchronous searches |
5 |
2000 |
For details on asynchronous processing, see Asynchronous Request Processing.
Understanding Request Limiting
Request limits refer to the size of your SOAP request. The maximum allowed size for a SOAP request is 100MB.
Understanding Governance Errors
The following faults are thrown because of other governance violations.
-
ExceededRecordCountFault – thrown if a request exceeds the allowed record count.
-
ExceededRequestLimitFault – thrown if the allowed number of concurrent requests is exceeded.
-
ExceededRequestSizeFault – thrown if a request exceeds 100M.
For more information about exceptions, refer to SOAP Web Services Error Handling and Error Codes.
For information about concurrency governance, see Web Services and RESTlet Concurrency Governance.