1. Home
  2. Systems
  3. NetSuite integration

NetSuite integration: build new links on REST web services, because SOAP stops in 2028.2

Yes, NetSuite has an API. Oracle wants every new integration built on REST web services with OAuth 2.0. SOAP web services stop working with release 2028.2, and the routes below differ most in how they sign in and how fast they can go.

Checked 18 November 2026

Does NetSuite have an API? Yes, and Oracle names REST web services as the one to build on

NetSuite opens several doors to outside software. Since release 2026.1, Oracle’s advice is that every new integration uses REST web services with OAuth 2.0. OAuth 2.0 is a standard way for one app to get limited access to another without sharing a password.

SuiteTalk REST web services let an outside system create, read, update and delete NetSuite records. SuiteQL, a SQL-like query language, runs through the same REST door. A RESTlet is custom SuiteScript that an outside system can call. SuiteScript is the code that runs inside NetSuite.

Scroll the table sideways to see every column.

Route What it does Limit to plan around Status on 18 November 2026
SuiteTalk REST web services Create, read, update and delete records A request times out after 15 minutes; size limit 104MB Oracle’s choice for all new work
SuiteQL through REST Read data with SQL-like queries At most 100,000 results per query Current
RESTlets Your own SuiteScript at a URL 5,000 usage units per script; 10MB per string Oracle’s fallback where REST has gaps
SOAP web services The older XML interface Needs token-based authentication No new builds from 2027.1; stops in 2028.2
SuiteAnalytics Connect ODBC, JDBC and ADO.NET reads Read-only; cannot update data Current; NetSuite2.com is the only data source
Connectors and iPaaS Ready-made flows from Oracle and others Share the account’s concurrency limit Check which NetSuite API each one calls

SuiteQL enforces the same role-based access as SuiteAnalytics Workbook. So a query only sees what its role may see.

SOAP web services and token-based sign-in have dated end points

Oracle dates these by release, not by calendar. NetSuite has two major releases each year, so each release comes about six months after the last. Count releases, not months.

  • 2026.1. Oracle’s advice from here on: build every new integration on REST web services with OAuth 2.0.
  • 2027.1. No new SOAP integration can be built. No new integration can use token-based authentication (TBA) for SOAP, REST web services or RESTlets. Every integration that uses NLAuth, an old sign-in method, stops working. PKCE, an added check on the OAuth 2.0 sign-in code, becomes required for new authorization code integrations.
  • 2027.2. Only the last SOAP endpoint is still supported and gets bug fixes. Oracle says 2025.2 is the last planned one.
  • Every release. Oracle disables the oldest unsupported SOAP endpoint.
  • 2028.2. Every SOAP endpoint is disabled, and SOAP integrations stop. Support for existing TBA integrations ends too, tentatively. SuiteAnalytics Connect is excluded from that end date. Scripts on SuiteScript 1.0 or 2.0 should be on SuiteScript 2.1 by then.

Existing links keep running until those dates. Oracle says existing integration records that use SOAP and TBA may still be updated until SOAP is fully removed. If a partner built your SOAP app, Oracle tells you to ask that partner for a timeline for a REST version. For SOAP apps built by NetSuite, Oracle says a REST version will come “in time”.

Oracle’s FAQ gives three reasons. SOAP lacks the latest business features, and new records have not reached it for a couple of years. It cannot use newer platform parts such as SuiteAnalytics Workbooks. And its token-based sign-in “does not meet modern security standards”. A separate Oracle comparison table adds that SOAP needs more calls than REST to finish a business flow.

Concurrency limits set the speed of every route

Concurrency is how many requests NetSuite will work on at once for your account. It has a hard cap. On contracts from June 2020 on, Oracle’s base limits are Standard 5, Premium 15, Enterprise 20 and Ultimate 20.

Each SuiteCloud Plus licence adds 10. Oracle’s own example is Ultimate with five licences: 20 + 5 x 10 = 70. SuiteCloud Plus licences are not part of any service tier. They are bought on top.

The limit belongs to the account, not to one app. Web services and RESTlet requests count together. Oracle’s AI Connector Service shares the same limit, and one AI prompt can fire several requests. A request over the limit gets an error, and Oracle says the client should retry it.

Two habits follow. Every integration should call the governanceLimits operation to learn its own number, as Oracle’s REST docs advise. And an admin should check the Integration Governance page before adding a new link. Five busy links on a Standard account share 5 slots.

REST web services cover most jobs, and RESTlets fill the gaps

Oracle says not to expect 100% parity of REST with SOAP. Where REST web services lack an object or a method, Oracle names RESTlets as the fallback. These are the REST gaps we check before we plan a job:

  • REST web services do not support custom sublists.
  • A REST query returns only record IDs and links, and only body fields work in query conditions.
  • REST web services need the SuiteTax feature, because legacy tax features are not supported. Oracle says legacy tax in REST is planned, but suggests SuiteTax instead.
  • The REST query service cannot run asynchronously. Any other REST request can, with the Prefer: respond-async header.

Every record conversion in SuiteScript, such as sales order to invoice, is also in REST web services.

RESTlets have their own limits. One can use up to 5,000 usage units per script, five times more than a Suitelet. Oracle allows each string in or out up to 10MB. RESTlet URLs accept only TLS-encrypted requests, and RESTlets created from release 2021.1 do not accept user credentials.

Oracle’s own integration tools each cover a narrow job

  • NetSuite Connector links NetSuite to ten storefronts and 3PLs: Amazon Seller Central, Amazon Vendor Central, BigCommerce, eBay, Magento 2, Shipstation, Shopify, Shopify POS, Walmart and WooCommerce. Our NetSuite and Shopify page covers its Shopify connector.
  • NetSuite Connector Platform is a SuiteApp that holds Oracle’s Salesforce Connector, which turns Closed Won opportunities into NetSuite sales orders. Its connectors are built on Oracle Integration Cloud. See NetSuite and Salesforce integration.
  • Oracle Integration offers a NetSuite Adapter, a no-code tool that uses SOAP. Its NetSuite REST Adapter uses REST and JSON instead. The REST Adapter can start a flow when a record is created or updated, and when one is deleted. It does this for the record types chosen when its NetSuite script is deployed.
  • CSV import is the most common way to move small and mid-sized data sets into NetSuite, Oracle’s help says. It suits a one-off load, not a running link.

Two common links sit outside Oracle’s tools. HubSpot’s own NetSuite app syncs CRM records, sales orders and financial data; see HubSpot and NetSuite integration. For EDI, Oracle’s help leaves the conversion to a NetSuite EDI partner; see NetSuite EDI integration.

iPaaS tools work, if you check which NetSuite API each connector calls

An iPaaS (integration platform as a service) is a hosted tool for building flows between apps. Oracle’s TBA end-of-support page names Boomi, Celigo, MuleSoft and Informatica as examples of connectors that may need new settings or a new version to move from TBA to OAuth 2.0.

So check two things before you commit to an iPaaS connector: which NetSuite API it calls, and how it signs in. MuleSoft shows why. Its NetSuite Connector is SOAP-based. Version 11.0 and later supports no REST-based operations. It connects with token-based authentication. A new connection on it meets the 2027.1 TBA cut-off first. A flow on it has to move before 2028.2, for example to MuleSoft’s separate NetSuite REST Connector, which signs in with OAuth 2.0.

A custom build fits when the job crosses systems or needs your own rules

A custom build runs on REST web services and OAuth 2.0, with RESTlets where REST has gaps. These are the facts it must design around:

  • An access token is valid for 60 minutes, so the integration refreshes it on a schedule.
  • The client secret shows only the first time the integration record is saved.
  • OAuth 2.0 is only available for RESTlets and REST web services.
  • Roles that need 2FA (two-factor sign-in) need it for API access too, with no user credentials.
  • A redirect URI must use https or a custom scheme. The http scheme is not supported.
  • One integration record can use both the authorization code grant and the client credentials (machine to machine) grant.
  • Inside NetSuite, a user event script is capped at 1,000 usage units and a scheduled script at 10,000.

An AI agent is a custom route too. NetSuite has adopted the Model Context Protocol (MCP), an open standard for linking AI models to data. Its AI Connector Service shares the same concurrency limit as every other link. See NetSuite AI agents.

Start with the narrowest tool that does the job

Start from the other system and the job. Then pick the narrowest tool that does it.

Scroll the table sideways to see every column.

If the job is Start with Why
Orders and stock with a listed storefront NetSuite Connector Oracle lists ten storefronts and 3PLs it supports
Closed Won deals from Salesforce Oracle’s Salesforce Connector Oracle’s own sync, run by a SuiteApp in NetSuite
Reporting reads into a BI tool SuiteAnalytics Connect Read-only, and Oracle says it suits data that changes rarely
Many systems with shared logic An iPaaS whose NetSuite connector uses REST One place for every flow, past 2028.2
A record or method REST lacks A RESTlet Oracle’s named fallback
Rules only your company has, or an AI agent A custom build on REST and OAuth 2.0 Full control of logic and retries

Our team has taken NetSuite live, and eight other ERPs

Our team has ERP go-lives on NetSuite, SAP, Odoo, Microsoft Dynamics, ERPNext, Xero, QuickBooks, Sage and custom ERPs. It has also built HubSpot to ERP integrations. For a new NetSuite account, start with NetSuite implementation.

The first call is free. We sign your NDA before you share any data, if you ask.

Questions

Does NetSuite have an API?

Yes. NetSuite has SuiteTalk REST web services for records, SuiteQL for queries, RESTlets for your own endpoints and SuiteAnalytics Connect for read-only reporting. It also has SOAP web services. But no new SOAP integration can be built from release 2027.1, and SOAP stops working with 2028.2. Oracle's advice is to build every new link on REST web services with OAuth 2.0.

How do I set up the NetSuite API?

An administrator turns on the features first. Enable REST Web Services on the SuiteCloud subtab, plus Client SuiteScript and Server SuiteScript, then check OAuth 2.0 under Manage Authentication. Next, create an integration record. Its client secret shows only on the first save, so copy it then. Access tokens last 60 minutes. Oracle advises against using the administrator role for the integration itself.

Is NetSuite HIPAA compliant?

Oracle gives no single yes or no for the whole product on the pages we read. On its page about AI features, it sorts them into three groups: attested for HIPAA, not yet assessed, and not subject to HIPAA. It says not to use unassessed AI features for ePHI (protected health data). For SuiteAnalytics Connect, the customer must make sure ePHI sent to other apps complies. Ask Oracle what your contract covers.

When does NetSuite SOAP stop working?

With release 2028.2, when Oracle disables every SOAP endpoint. Two earlier dates matter too. From 2027.1, no new SOAP integration can be built. From 2027.2, only the 2025.2 endpoint is still supported. Oracle gives release names, not calendar dates, and NetSuite ships two major releases a year. So count releases, not months.

How many API requests can NetSuite handle at once?

It depends on your service tier. Oracle's base limits are 5 for Standard, 15 for Premium, 20 for Enterprise and 20 for Ultimate, on contracts from June 2020 on. Each SuiteCloud Plus licence adds 10, and those licences are bought on top of the tier. Every web service and RESTlet call on the account shares that one limit.

Do we need an official NetSuite partner to do this?

Not for this work. What decides an integration is a team that knows NetSuite from the inside and builds on Oracle's published APIs, such as REST web services. Our team has taken NetSuite live and has built HubSpot to ERP integrations. You license NetSuite from Oracle or its reseller, and we take the consulting, setup, data move and integration build from there.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Pages in this section

  • HubSpot and NetSuiteHubSpot's own NetSuite app syncs contacts, companies, deals, orders and invoices, and makes sales orders from deals. Setup steps and limits, checked.
  • NetSuite and SalesforceOracle's Salesforce Connector turns Closed Won opportunities into NetSuite sales orders. How it compares with MuleSoft and a custom API build.
  • NetSuite and ShopifyOracle's NetSuite Connector pulls Shopify orders every 20 minutes and pushes products every 60. Its limits, B2B rules and when a custom build fits.
  • NetSuite EDIOracle's help leaves EDI translation to an EDI provider. How X12 850, 856 and 810 map to NetSuite records, how providers connect, and where AS2 fits.

Check your NetSuite links against the 2027.1 and 2028.2 dates

The first call is free. Bring the list of systems that touch NetSuite today, and we can go through which ones use SOAP or token-based sign-in.

Book a NetSuite integration call