This notice is intended for all customers with REST web services enabled in their account.
You are receiving this follow-up to our previous notification that NetSuite 2026.2 would standardize the status.id values returned by REST Web Services for transaction records across all transaction types. This change has been postponed and is now targeted for NetSuite 2027.1. No action is required for this change in NetSuite 2026.2.
What’s Changing?
The planned change to status.id values will not be included in NetSuite 2026.2. It is now targeted for NetSuite 2027.1.
In NetSuite 2027.1, the status.id field returned in REST GET responses for transaction records will be updated to return the documented single-letter status codes (A, B, D, E, and V) across all transaction types. Currently, some transaction types return a text value, such as "Open," in status.id, while other transaction types return the expected letter code. The text values duplicate the values returned by the status.refName field.
This change will align REST behavior with the published API documentation and provide consistent responses across all transaction types.
Required Actions
No action is required for this change in NetSuite 2026.2.
Before your account is upgraded to NetSuite 2027.1:
- Review REST integrations that use status.id in transaction REST GET requests.
- Update any logic, filters, mappings, and validations that expect text values from status.id.
- If your integration requires a human-readable status label, use status.refName instead of status.id.
- Test affected workflows in a NetSuite 2027.1 sandbox or Release Preview account before your production account is upgraded.
For more information, see NetSuite REST API Browser: Record API v1, SuiteAnswers ID 89313. If you require assistance or more information, please contact NetSuite Customer Support.