NetSuite SOAP endpoint changes: What you need to know

Oracle NetSuite has announced a major change to its SOAP web services endpoint policy. Starting with the 2026.1 release, SOAP endpoints will no longer be issued on a regular schedule. Instead, new endpoints will be introduced only when there is a clear business or technical need.

This policy shift affects how organizations manage integrations that rely on SOAP. At Rand Group, we want to ensure your systems remain stable and secure while you prepare for the transition.

Starting with the NetSuite 2026.1 release, Oracle NetSuite will no longer provide a new SOAP web services endpoint with each release. Instead, new SOAP endpoints will only be delivered when there is a business, technical, or other compelling reason. This means that regular, scheduled SOAP endpoint releases are coming to an end.

All existing SOAP web services endpoints will continue to be supported for three years after their release date. However, with each new NetSuite release, the oldest SOAP web services endpoint will be retired automatically. The 2025.2 SOAP web services endpoint will be the last to follow the traditional release schedule.

Organizations using custom or third-party SOAP integrations are most affected by this change.

If you are using only Oracle NetSuite solutions that are developed, owned, and maintained by Oracle NetSuite—such as NetSuite Connector, NSPOS, or SuiteProjects Pro—you do not need to take any action. These solutions will continue to operate smoothly under the new policy.

However, if your organization relies on custom integrations or third-party solutions that use SOAP web services, it’s essential to take note of these changes.

Rand Group recommends a proactive approach to protect your integrations and minimize disruption:

• Upgrade to the 2025.2 endpoint: When this endpoint becomes available, update your client applications and integrations to use it. This will give you the maximum support window of three years from the release date.
• Adopt REST web services with OAuth 2.0: For new integrations, use REST APIs with OAuth 2.0. REST is NetSuite’s recommended standard and offers modern, scalable, and secure integration methods.
• Evaluate and migrate legacy SOAP integrations: Begin planning now to move away from SOAP where possible. Migration ensures your integrations align with NetSuite’s long-term roadmap.

• What happens if I don’t upgrade to the 2025.2 SOAP endpoint?
  If you remain on an older endpoint, your integrations may stop working when that endpoint is retired. This can disrupt critical business processes.
• Why is NetSuite moving from SOAP to REST APIs?
  REST APIs are NetSuite’s recommended integration standard because they are more scalable, secure, and easier to maintain. They also align with industry best practices.
• How long does NetSuite support SOAP endpoints?
  Each SOAP endpoint is supported for three years after its release. With every new release, the oldest supported endpoint is retired.

The move away from routinely scheduled SOAP endpoints is a significant shift, but it also brings an opportunity to modernize your business processes and integrations. REST APIs provide streamlined, scalable, and secure integration methods that future-proof your technology investments.

At Rand Group, we are committed to helping you stay ahead of industry changes. Our team will partner with you through every step of the transition, from readiness assessments to deployment and support. If you have questions or wish to start planning your migration, contact Rand Group today.

Let’s ensure your NetSuite environment remains secure, efficient, and ready to support your business growth well into the future.