REST Web Services Gets Attach/Detach, Batch Ops, create-form, selectOptions — SOAP Sunset Continues

New REST Web Services Operations

Attach and Detach

You can now define or remove relationships between two record instances via REST. This mirrors the SOAP attach/detach operations that have existed for years.

Endpoint pattern:

/services/rest/record/v1/{recordType}/{id}/!attach/{targetType}/{targetId}

Example: /services/rest/record/v1/customer/660/!attach/contact/106

Limitation: Only contact and file record types are supported for attach/detach in this release. If you need to attach other record types (e.g., attaching files to custom records beyond these two), you still need SOAP or SuiteScript workarounds.

Homogeneous Batch Operations

You can now add, update, delete, or upsert multiple instances of the same record type in a single REST request. Key details:

• Operations are asynchronous — you will get a job/task ID back, not immediate results. Plan your integration flow accordingly (poll for completion or use a callback pattern).
• This targets bulk/ETL scenarios: large-scale imports, mass updates, and bulk deletes.
• Reduces round-trips and governance overhead compared to looping individual REST calls.

Oracle's docs call these "homogeneous" to distinguish from potential future mixed-type batches. For now, all records in a single batch request must share the same record type.

create-form Operation

The create-form operation returns a record form with all fields prepopulated with defaults, including default line IDs on sublists. This lets you emulate the UI's initialization behavior in REST.

Practical example: When billing a sales order via REST, you can now load an invoice via create-form referencing the related sales order, and the invoice fields will be initialized from the SO — just like clicking "Bill" in the UI. Your code then patches only the fields it needs before submitting.

This is significant for anyone building transaction-creation flows in external apps who previously had to manually replicate NetSuite's field-defaulting logic.

selectOptions Operation

Retrieves valid select/dropdown options for a specific field on a specific record. Use cases:

• Building external UIs that mirror NetSuite dropdowns without hardcoding values.
• Fetching options for fields whose referenced record type is not yet REST-exposed.
• Fetching options when the current role lacks permission to the referenced record type directly.

Note: Results are role-sensitive — the same field can return different options for different roles. Cache with caution.

New REST-Supported Records

2026.1 adds 35+ record types to REST web services. Notable additions grouped by area:

• Payments: Automated Clearing House, General Token, Payment Card, Payment Card Token (requires Payment Instruments and Credit Card Payments features)
• Campaign/Marketing: Campaign Audience, Category, Channel, Family, Offer, Search Engine, Subscription, Template, Vertical, Sales Campaign, Entity Group (requires Marketing Automation and related CRM features)
• Inventory: Inventory Status, Item Supply Plan, Lot Numbered Assembly Item, Lot Numbered Inventory Item, Serialized Assembly Item, Serialized Inventory Item
• Financials: Budget Exchange Rate, Budget Import, Fair Value Formula, GL Audit Numbering Sequence, Paycheck Journal, Tax Control Account, Tax Group, Tax Schedule
• CRM/Support: Lead Source, Partner Category, Support Case Origin/Priority/Status/Type, Win/Loss Reason
• Pricing: Sale Price Rule, Sale Price Rule Entry
• Commerce: Site Category

Each record requires specific features to be enabled. Refer to Oracle's REST API Browser for the full schema and field definitions.

SOAP Endpoint Deprecation Timeline

Oracle reaffirms that 2025.2 is the last planned SOAP endpoint. Future SOAP endpoints will only be released if required for critical business/technical reasons. The deprecation schedule:

• 2025.2 endpoint: Supported (S) through 2028.1, then disabled in 2028.2.
• 2025.1 and 2024.2: Supported through 2027.1, then available-without-support (U) in 2027.2–2028.1, disabled in 2028.2.
• 2024.1: Supported through 2026.2, unsupported-available through 2028.1, disabled in 2028.2.
• 2023.2 and older: Already in unsupported-available (U) status or being phased to disabled (-).
• 2019.1 and 2018.2: Already disabled as of 2026.1.
• 2019.2: Disabled starting 2026.2.
• 2020.1: Disabled starting 2027.1.

Status key: S = Supported, U = Available without support, - = Disabled/unavailable.

MCP AI Connector Service Updates

The Execution Log on integration records now includes a new AI Connector Service (MCP) subtab alongside the existing SOAP, REST, and RESTlets tabs. Columns include: Time, Duration, Status, User email, HTTP status code, Method, and URL.

Additionally (noted in the title but detail is sparse), Oracle mentions support for consolidated reports and a new SuiteQL tool in MCP standard tools, plus general enhancements to MCP standard tools. The release notes provide no further technical specifics on these MCP enhancements — check Oracle's MCP documentation for details as they become available.

What to Do

1. If you are still on SOAP: Begin migration planning to REST web services now. Map your current SOAP operations to REST equivalents. The new batch operations, attach/detach, and create-form close major feature gaps that previously justified staying on SOAP. Target completing migration before your endpoint version reaches unsupported (U) status.
2. If you use REST integrations: Evaluate the new create-form operation for any transaction-creation flows where you manually replicate UI defaulting logic — this can simplify your code significantly. Evaluate selectOptions if you maintain external UIs with NetSuite-sourced dropdowns.
3. If you do bulk data operations: Test the new async batch operations against your current loop-based REST calls. Note the async pattern — you will need to handle job polling or callbacks instead of synchronous responses.
4. Review newly supported records: If you have SuiteScript or SOAP workarounds for any of the 35+ newly REST-supported records, consider migrating those integrations to REST for consistency and future-proofing.
5. Enable required features: Many new REST records require specific features (Payment Instruments, Marketing Automation, Lot Tracking, etc.). Verify these are enabled in your account before attempting REST calls against those record types.
6. MCP users: Check the new Execution Log subtab on your integration records for AI Connector Service call visibility.