Skip to main content

Netsuite Feeds

NetSuite is Oracle's cloud ERP suite, covering financials, accounting, order management, inventory, CRM, and commerce for growing businesses. The Netsuite Feeds connector is a source-only, multi-feed ELT connector that reads from the NetSuite SuiteTalk REST Record Service. Rather than configuring one endpoint at a time, Nexla discovers the record types available in your NetSuite account and ingests each selected record type as its own feed, with a choice of full-refresh or incremental sync per feed.

Netsuite Feeds icon

Power end-to-end data operations for your Netsuite Feeds API with Nexla. Our bi-directional Netsuite Feeds connector is purpose-built for Netsuite Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Netsuite Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Netsuite Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

The Netsuite Feeds connector authenticates to the NetSuite SuiteTalk REST Record Service using token-based authentication (TBA), NetSuite's OAuth 1.0 based method for machine-to-machine access. Before creating a credential in Nexla, an administrator must enable the required features, create an integration record, and issue an access token. This produces six values: your NetSuite account ID, a consumer key and consumer secret (from the integration record), and an access token and token secret (from the access token), plus the OAuth realm.

Enable the required features​

  1. In NetSuite, navigate to Setup > Company > Enable Features.

  2. On the SuiteCloud tab, under SuiteTalk (Web Services), enable REST Web Services.

  3. Under Manage Authentication, enable Token-Based Authentication.

  4. Click Save.

Find your account ID​

Your NetSuite account ID is part of your REST API domain. NetSuite REST requests are sent to https://<account_id>.suitetalk.api.netsuite.com, where <account_id> is your account ID in lowercase (for example, 1234567, or 1234567-sb1 for a sandbox account). The account ID is visible under Setup > Company > Company Information in the Account ID field. The same value, typically in uppercase, is used as the OAuth realm.

Create an integration record​

The integration record produces the consumer key and consumer secret.

  1. Navigate to Setup > Integrations > Manage Integrations > New.

  2. Enter a unique Name and, optionally, a description.

  3. Under Authentication, select Token-Based Authentication, and clear the TBA: Authorization Flow checkbox.

  4. Click Save.

  5. On the confirmation screen, copy the Consumer Key and Consumer Secret.

Important

The consumer key and consumer secret are shown only once, on the confirmation screen. Copy both values before navigating away. If you lose them, you must reset the integration record's credentials to generate a new pair.

Create an access token​

The access token produces the token ID and token secret. The role you assign determines which records the token can read, so use a role with permission to the record types you plan to ingest.

  1. Navigate to Setup > Users/Roles > Access Tokens > New.

  2. In the Application Name field, select the integration record you created above.

  3. In the User field, select the integration user, and in the Role field, select the role that grants access to the required records.

  4. Click Save.

  5. Copy the Token ID and Token Secret.

Important

The token ID and token secret are shown only once. Copy both values before navigating away. If you lose them, revoke the token and create a new one.

For complete details on enabling and configuring token-based authentication, see the NetSuite documentation on Setting Up Token-based Authentication.

Authenticate​

Credentials required​

Authorization to access your Netsuite account.

FieldRequiredSecretDescription
Netsuite Account IDYesNoAccount ID is a part of your REST API Domain name
OAuth1 Consumer KeyYesNoNetsuite Feeds OAuth1 Consumer Key
OAuth1 Consumer SecretYesYesNetsuite Feeds OAuth1 Consumer Secret
OAuth1 Access TokenYesYesNetsuite Feeds OAuth1 Access Token
OAuth1 Access Token SecretYesYesNetsuite Feeds OAuth1 Token Secret
OAuth1 Realm (Account ID/Company Identifier)YesNoNetsuite OAuth1 Realm

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. Use them to identify the NetSuite account or environment (production versus sandbox) that this credential represents.

  3. Enter your NetSuite account ID in the Netsuite Account ID field. This is the value that forms your REST API domain (for example, 1234567 or 1234567-sb1).

  4. Enter the consumer key and consumer secret from your integration record in the OAuth1 Consumer Key and OAuth1 Consumer Secret fields.

  5. Enter the token ID and token secret from your access token in the OAuth1 Access Token and OAuth1 Access Token Secret fields.

  6. Enter your OAuth realm in the OAuth1 Realm (Account ID/Company Identifier) field. This is your NetSuite account ID, typically entered in uppercase (for example, 1234567 or 1234567_SB1). Nexla signs each request using HMAC-SHA256 and includes the realm in the OAuth header.

  7. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Netsuite Feeds flows.

Use as a data source​

How This Connector Works​

The Netsuite Feeds connector is a source-only, multi-feed ELT connector built on the NetSuite SuiteTalk REST Record Service. Instead of configuring one endpoint at a time, you select the NetSuite record types you want, and Nexla ingests each selected record type as its own feed.

  • Discovery: When you create the source, Nexla queries the NetSuite REST metadata catalog (/services/rest/record/v1/metadata-catalog/) to discover the record types available in your account and presents them for selection.

  • Two-step reads: For each selected feed, Nexla first pages through the record list to collect record links, then follows each link to retrieve the full record. The id field is used as the primary key to uniquely identify records within a feed.

  • Parallel ingestion: Selected feeds are ingested in parallel (up to several feeds at a time), so a single source can pull many NetSuite record types on the same schedule.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Netsuite Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to your NetSuite account and click Next; or, create a new Netsuite Feeds credential for use in this flow.

Select the Objects to Ingest​

After authenticating, Nexla discovers the record types available from your NetSuite account and lists them for selection. Select one or more record types to ingest — each selected record type becomes its own feed. The specific record types available depend on the permissions of the role attached to your access token; common examples include contact, customer, invoice, salesOrder, and vendor.

NetSuite record list responses are paginated. Nexla follows the offset-based pagination automatically while reading each feed, so each run ingests all available records for the selected record types.

Choose a Sync Strategy​

For each feed, choose one of the following sync strategies:

  • Full Refresh — Reads the complete current set of records for the record type on every run. Use this for reference or dimension data, or when you need a full snapshot.

  • Incremental Sync — Reads only records changed since a cursor time, using the record type's incremental query column. Configure the Incremental Syncs: Lookback Time field to set how far back the first run looks. Use a relative expression such as {now-24} (the default, 24 hours back; the default unit is hours) or {now-1}, or an absolute date in yyyy-MM-dd format. Subsequent runs advance the cursor from the previous successful run.

Incremental Sync is available for record types that expose a system-managed "last modified" field for querying. Record types without such a field should be ingested using Full Refresh.

Schedule and Activate​

Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, Nexla ingests every selected feed using its configured sync strategy and organizes the retrieved data into one or more Nexsets.

Reference​

For NetSuite record schemas, field definitions, and the full list of record types available through the REST Record Service, see the NetSuite REST API Browser and the SuiteTalk REST Web Services documentation.