Could native REST replace some custom integration code?

Why it matters

Native REST may let you remove some custom code if it supports the operation and its requirements.

First step

Map one candidate search or file operation before considering replacement.

Suggested owner

Integration owner

Who should check?

Integration owners maintaining custom code to run existing saved searches or move files and folders into and out of NetSuite.

Availability, not a migration deadline

September 2026 minor release (NetSuite 2026.2)REST saved-search execution and File Cabinet capabilities are documented as available improvements.

Check your Oracle account notice before scheduling an update.

What to do next

Map the current operation to documented native REST capabilities and limits.
Compare authentication, permissions, file size and execution behavior with the actual business requirement.
Test one agreed operation, compare the results with the current integration, and keep a way to restore it before removing working code.

What we’ll review

Operations, search IDs, criteria overrides, folder permissions, file sizes, authentication, volume, paging, retry behavior and external-system ownership for an agreed integration set.

See the approach

See a related project

See our integration engineering approach →

Sources and updates

Oracle documentation

NetSuite 2026.2 September minor release ↗Oracle publication/update date not stated on this page. · Source checked: 2026-10-20

Using saved searches in REST web services ↗Oracle publication/update date not stated on this page. · Source checked: 2026-10-17

Working with File Cabinet records in REST ↗Oracle publication/update date not stated on this page. · Source checked: 2026-10-17

Update history

2026-10-17 — Added this guide using existing Oracle documentation.

Follow this topic via RSS

Let’s discuss your NetSuite needs

Tell us what you need help with.

This form sends us a message. It does not connect to NetSuite or sign you up for marketing emails.