> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/sales/netsuite/how-to-connect.md).

# How to Connect

Coupler.io connects to NetSuite using **Token-Based Authentication (TBA)**. This requires a few one-time setup steps in your NetSuite account to generate the credentials needed for the connection: Realm (Account ID), Consumer Key, Consumer Secret, Token Key, and Token Secret.

Follow the steps below in your NetSuite account before filling out the connection form in Coupler.io.

## Step 1: Obtain your Realm (Account ID)

1. Log in to your NetSuite account.
2. Go to **Setup » Company » Company Information**.
3. Copy your **Account ID (Realm)**. It should look like `1234567` for a Production environment, or `1234567_SB2` for a Sandbox environment.

## Step 2: Enable required features

1. Go to **Setup » Company » Enable Features**.
2. Open the **SuiteCloud** tab.
3. Scroll to the **SuiteScript** section and enable **CLIENT SUITESCRIPT** and **SERVER SUITESCRIPT**.
4. Scroll to the **Manage Authentication** section and enable **TOKEN-BASED AUTHENTICATION**.
5. Scroll to the **SuiteTalk (Web Services)** section and enable **REST WEB SERVICES**.
6. Save your changes.

## Step 3: Create an Integration record (Consumer Key and Consumer Secret)

1. Go to **Setup » Integration » Manage Integrations » New**.
2. Enter a name for the integration — we recommend `coupler-integration`.
3. Make sure **State** is set to **Enabled**.
4. In the **Authentication** section, enable **Token-Based Authentication**.
5. Save your changes.
6. Your **Consumer Key** and **Consumer Secret** will be displayed once — copy and store them somewhere safe, as they won't be shown again.

## Step 4: Set up a role

1. Go to **Setup » Users/Roles » Manage Roles » New**.
2. Enter a name for the role — we recommend `coupler-integration-role`.
3. Open the **Permissions** tab and configure the following (all required):
   * **Transactions** — manually add all dropdown entities with either Full or View access.
   * **Reports** — manually add all dropdown entities with either Full or View access.
   * **Lists** — manually add all dropdown entities with either Full or View access.
   * **Setup** — manually add all dropdown entities with either Full or View access, **including "Log in using Access Tokens" and "Web Services"**.

{% hint style="warning" %}
Completing all required permission steps correctly is essential to avoid sync issues later. If you rename or customize any object in NetSuite, revisit this role's permissions to reflect those changes. Permission naming can vary slightly by NetSuite version/edition, so double-check the exact labels in your own instance.
{% endhint %}

## Step 5: Assign the role to a user

1. Go to **Setup » Users/Roles » Manage Users**.
2. Click the name of the user you want to grant access to.
3. Click **Edit**.
4. Open the **Access** tab.
5. From the dropdown, select the `coupler-integration-role` you created in Step 4.
6. Save your changes.

## Step 6: Create an Access Token

1. Go to **Setup » Users/Roles » Access Tokens » New**.
2. Select an **Application Name**.
3. Under **User**, select the user you assigned the role to in Step 5.
4. Under **Role**, select `coupler-integration-role`.
5. Under **Token Name**, enter a descriptive name — we recommend `coupler-integration-token`.
6. Save your changes.
7. Your **Token Key** and **Token Secret** will be displayed once — copy and store them somewhere safe, as they won't be shown again.

Once you have all five credentials (Realm, Consumer Key, Consumer Secret, Token Key, Token Secret), enter them into the NetSuite connection form in Coupler.io to complete the connection.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/sales/netsuite/how-to-connect.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.