New Attach and Detach Operations in REST Web Services
With the new attach and detach operations, you can define or remove a relationship between two record instances. For example, you can associate a contact record instance with a partner record instance, or you can associate a file record instance with an opportunity record instance. Currently, you can attach or detach contact records and file records only. To attach or detach two records, you must use the record type and IDs of the record instances. For example: …/services/rest/record/v1/customer/660/!attach/contact/106 For more information, see the help topic Attach and Detach Operations. For information about every available operation in REST web services, see the help topic SOAP Web Services and REST Web Services Operations. Support for Homogeneous Batch Operations in REST Web
Services
With the new homogeneous batch operations, you can add, update, delete, or upsert multiple instances of the same record type in a single REST request. Batch operations reduce the number of network requests by processing multiple records in one request, minimizing latency and server load. This approach is useful for large-scale data imports, updates, and deletions, because it improves system performance and user experience. Batch operations in REST web services are executed asynchronously. For more information, see the help topic Batch Operations. For information about every available operation in REST web services, see the help topic SOAP Web Services and REST Web Services Operations.
New create-form Operation in REST Web Services
The create-form operation returns a record form with all fields prepopulated. This operation enables you to see all default fields and the line IDs of default lines on a record, and you can modify these values before submitting the record. With the create-form operation, you can emulate a NetSuite UI workflow by prepopulating fields on transaction line items with values from a related record. Your REST web services application can then modify only the values it needs to before submitting the record.
For example, in the UI, when you bill a sales order, an invoice record is loaded with fields populated with
values from the sales order. When loading an invoice record in REST web services, you can reference the related sales order record to initialize fields with values from that sales order. For more information, see the help topic Create-form Operation. For information about every available operation in REST web services, see the help topic SOAP Web Services and REST Web Services Operations.
New selectOptions Operation in REST Web Services
With the new selectOptions operation, you can retrieve valid select options for specific records and fields. This operation is useful if you are creating an application UI that needs to mimic NetSuite UI logic, if the referenced record type is not yet exposed to REST web services. The selectOptions operation is also useful when the logged-in user’s role doesn’t have permission to the instances of the referenced record type. The selectOptions operation can return different results for the same field for different roles. For more information, see the help topic selectOptions Operation. For information about every available operation in REST web services, see the help topic SOAP Web Services and REST Web Services Operations.
REST Web Services Supported Records in 2026.1
In 2026.1, the following records became fully supported in REST web services.
Record Type Notes
Support Case Origin You must enable the CRM > Customer Support and Service feature to work with this record in REST web services. Support Case Priority You must enable the CRM > Customer Support and Service feature to work with this record in REST web services. Support Case Status You must enable the CRM > Customer Support and Service feature to work with this record in REST web services. Support Case Type You must enable the CRM > Customer Support and Service feature to work with this record in REST web services. For a list of every supported record, see the help topic REST Web Services Supported Records. You can also see the list of supported records in the REST API browser. For more information about working with the browser, see the help topic The REST API Browser.
SOAP Web Services Endpoint Availability
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 was 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 following table shows the endpoint version and its status in future NetSuite release: S: Supported endpoint
U: Available endpoint without support
-: Disabled, unavailable endpoint
Endpoint NetSuite NetSuite NetSuite NetSuite NetSuite NetSuite
Version/NetSuite 2026.1 2026.2 2027.1 2027.2 2028.1 2028.2
Release
2025.2 S S S S S - 2025.1 S S S U U - 2024.2 S S S U U -
Endpoint NetSuite NetSuite NetSuite NetSuite NetSuite NetSuite
Version/NetSuite 2026.1 2026.2 2027.1 2027.2 2028.1 2028.2
Release
2024.1 S S U U U - 2023.2 S U U U U - 2023.1 U U U U U - 2022.2 U U U U U - 2022.1 U U U U U - 2021.2 U U U U U - 2021.1 U U U U - - 2020.2 U U U - - - 2020.1 U U - - - - 2019.2 U - - - - - 2019.1 - - - - - - 2018.2 - - - - - - For more information, see the Removal of SOAP Web Services and the SOAP Removal Plans FAQ. New Subtab in Execution Log of Integration Records for AI
Connector Service (MCP)
When you go to the Execution Log of an integration record, along with the SOAP Web Services, REST Web Services, and RESTlets subtabs, you can now also find one for AI Connector Service (MCP). The log information in respective columns:
- Time
- Duration
- Status
- User email
- HTTP status code
- Method
- URL