Skip to main content
Feedback

NetSuite REST (Tech Preview) connector

The NetSuite REST connector uses the NetSuite REST API to move data into and out of your NetSuite account. It supports Standard and Custom record types and provides Browse capability to automatically discover available object types and import their field definitions.

warning

This connector is in Technology Preview status. It should not be used in a production environment or with production data. For more information, see the Feature release stages page.

Overview

The NetSuite REST connector communicates with NetSuite over HTTPS using JSON. It connects to the NetSuite record REST API (/services/rest/record/v1) and supports the following operations:

  • Create — Insert new Standard or Custom object records into NetSuite.
  • Query — Retrieve records based on filter criteria.
  • Update — Modify an existing record using its internal ID.
  • Upsert — Insert or update a record based on an external identifier.
  • Delete — Remove an existing record using its internal ID.

Standard and Custom Record Types

The NetSuite REST connector exposes all Standard and Custom record types available in your NetSuite account. You can use the Browse capability to discover available object types and import their JSON schema definitions, which automatically generate request and response profiles for use in your integration process.

Error Processing

The connector surfaces errors from both NetSuite API responses and from internal validation. NetSuite error responses follow this format:

{Title}: [ErrorCode: {code}]. {detail}

HTTP status codes are mapped to operation statuses as follows:

HTTP Status RangeOperation Status
2xxSuccess
4xx (e.g., 400, 401, 404, 422)Application Error
5xx (e.g., 500)Failure

Connector Configuration

To configure a connector to communicate with NetSuite, set up two components:

  • NetSuite REST connection — Stores authentication credentials and the Base URL.
  • NetSuite REST operation — Specifies the object type and the action to perform (Create, Query, Update, Upsert, or Delete).

After building your connection and operation, set up your NetSuite REST connector step within a process.

Prerequisites

Before configuring the NetSuite REST connector, ensure the following:

  • The Base URL of your NetSuite instance is available (format: https://{NS_Account_ID}.suitetalk.api.netsuite.com)

  • Your NetSuite account has REST web services enabled.

  • Create a custom role

  • Assign the role to the appropriate user

Integration Record

  • For Token-Based Authentication: Enable token-based authentication for your NetSuite account. While connecting using Token Based Authentication, copy the Consumer Key and Consumer Secret from Integration Record and paste into the Consumer Key and Consumer Secret properties in the connection.

    note
    • Important: The Boomi NetSuite REST Integration Record (SuiteApp Bundle ID: 587997) has not yet been published on the NetSuite Marketplace. Because TBA requires the Consumer Key and Consumer Secret embedded in this bundle, TBA cannot be fully configured at this time.
    • Recommended alternative: Use OAuth 2.0. OAuth 2.0 (Authorization Code or Client Credentials) allows you to configure your own Integration Record in NetSuite without depending on the marketplace bundle, and is the direction all new integrations should take — NetSuite is deprecating Token-Based Authentication for new integrations from release 2027.1.

:::

  • For OAuth 2.0 Authorization Code: Enable Authorization Code Grant.
    While connecting using OAuth 2.0, Authorisation Code, the Client ID and Client Secret from Integration Record in the Boomi SuiteApp are not embedded in the connector.
    Instead, you copy these values from the Integration Record and paste into the Client ID and Client Secret properties in the connection.

  • For OAuth 2.0 Client Credentials (JWT): Enable Client Credentials (Machine to Machine) Grant
    While connecting using OAuth 2.0, Client Credentials, the Client ID from Integration Record in the Boomi SuiteApp is not embedded in the connector.
    Instead, you copy the Client ID value from the Integration Record and paste into the Issuer property in the connection.

Certificate

  • For OAuth 2.0 Client Credentials (JWT): A NetSuite Integration record with the Client Credentials (Machine to Machine) grant enabled is configured, a Public X.509 certificate has been created and uploaded to NetSuite's OAuth 2.0 Client Credentials setup, and the certificate's .pfx (containing private key) file has been imported as an X.509 Certificate component in Boomi.
On this Page