Skip to main content

NetSuite Connections and Settings

Connect iPaaS with Oracle NetSuite for efficient data exchange for inventory, customers, and transactions.

NetSuite Connections and Settings

Integrate iPaaS.com with NetSuite to enable seamless data synchronization for customers, products and inventory, transactions, and related records. This article is the ongoing reference for the connection — what each setting does, how authentication works, and what is required. For the first-time, step-by-step setup (including the NetSuite bundle, certificate generation, and the supporting customizations), see NetSuite Installation Instructions.

Prerequisites

Before you can connect to NetSuite, the prerequisite IPaaS webhooks bundle must be installed in your NetSuite account — see The NetSuite iPaaS.com Bundle. The bundle provisions the webhook scripts, custom fields, and custom records the integration relies on.

Configuration Details

You will need the following to connect (all are produced during the NetSuite setup described in NetSuite Installation Instructions):

  • Account ID — your NetSuite account identifier, taken from your NetSuite dashboard URL.

  • API URL — the base URL for NetSuite REST access, in the format https://{AccountID}.suitetalk.api.netsuite.com/services/rest/record/v1.

  • Consumer ID — generated during NetSuite OAuth 2.0 Machine-to-Machine (M2M) authentication setup.

  • Certificate ID — generated when you create and upload your OpenSSL certificate in NetSuite.

  • Certificate Private Key — the private key from your OpenSSL certificate.

  • Environment — only Production is supported.

Configure Subscription Settings

Configure your subscription in iPaaS.com using the fields below.

Field

Description

Required

Example

Name

A unique name for the subscription.

Yes

NetSuite - Production

Versions

Select the latest version from the dropdown.

Yes

v1.0

Account ID

Unique identifier for your NetSuite account.

Yes

td2819981

API URL

Base URL for NetSuite API access.

Yes

https://{AccountID}.suitetalk.api.netsuite.com/services/rest/record/v1

Consumer ID

Generated during Machine-to-Machine (M2M) authentication.

Yes

Provided after setup

Certificate ID

Generated during OpenSSL certificate creation and uploaded in NetSuite.

Yes

Provided after setup

Certificate Private Key

Key generated during OpenSSL certificate setup.

Yes

Provided after setup

Environment

Current valid value is "Production".

No

Production

Inventory Search Days

Defines the polling window for inventory updates, in days.

No

0

Authentication Methods

NetSuite authentication uses OAuth 2.0 Client Credentials (Machine-to-Machine) with a client certificate:

  1. A NetSuite integration record is created with Client Credentials (M2M) Grant, RESTlets, and REST Web Services enabled.

  2. An OpenSSL certificate is generated and uploaded to NetSuite's OAuth 2.0 Client Credentials (M2M) Setup, mapped to the integration application and an Administrator role.

  3. NetSuite returns a Consumer ID, Certificate ID, and Certificate Private Key, which are entered into the iPaaS.com Subscription Settings above. iPaaS.com uses them to obtain an access token for each NetSuite REST call.

The complete, step-by-step certificate generation and upload procedure (with screenshots) is in NetSuite Installation Instructions. To rotate credentials, generate a new certificate, upload it in NetSuite, and update the Certificate ID and Certificate Private Key in the Subscription Settings.

Initialization Support

The following reference data types support initialization and can be transferred in bulk:

  • Alternate Id Type TO iPaaS.com

  • Customer Category TO iPaaS.com

  • Location TO iPaaS.com

  • Payment Method TO iPaaS.com

  • Shipping Method TO iPaaS.com

Other record types — customers, products and the other item types, and transactions — are not bulk-initialized; they transfer on demand from the Manual Sync page or on their create/update events. See NetSuite Known Limitations for details.

Throttling

Throttling ensures NetSuite's API is not overwhelmed by excessive API calls, preserving system performance during heavy data transfers. The throttling fields are required, but their values are pre-populated by the integration settings. For more details, see Subscription Configuration – Edit.

Related Documents

Did this answer your question?