NetSuite is a leading cloud-based Enterprise Resource Planning (ERP) platform that helps businesses manage finance, operations, customer relationships, and more from a unified system. Its robust suite of applications streamlines workflows automates processes and provides real-time data insights.
To extend its functionality, NetSuite offers a comprehensive set of APIs that enable seamless integration with third-party applications, custom automation, and data synchronization.
Learn all about the NetSuite API in our in-depth Nestuite API Guide
This article explores the NetSuite APIs, outlining the key APIs available, their use cases, and how they can enhance business operations.
Key Highlights of NetSuite APIs
The key highlights of NetSuite APIs are as follows:
- SuiteTalk (SOAP & REST) – Provides programmatic access to NetSuite data and functionality for seamless integration with external applications. Supports both SOAP and REST web services.
- SuiteScript – A JavaScript-based API that enables custom business logic and automation within NetSuite, including workflows, user event scripts, and scheduled scripts.
- REST Web Services – A modern, lightweight API with JSON-based data exchange, ideal for real-time integrations and improved performance over SOAP.
- SOAP Web Services – A robust API for complex integrations, offering structured XML-based communication and extensive support for NetSuite's data model.
- SuiteAnalytics Connect – Enables direct access to NetSuite data via ODBC, JDBC, and ADO.NET for advanced reporting, analytics, and external BI tool integration.
- Token-Based Authentication (TBA) – Enhances security and scalability by allowing API access without storing user credentials using OAuth-style token authentication.
- OData Support—Integrates with business intelligence tools that support the OData protocol to facilitate easy data extraction for reporting and analytics.
These APIs empower developers to build custom solutions, automate workflows, and integrate NetSuite with external platforms, enhancing operational efficiency and business intelligence.
This article gives an overview of the most commonly used NetSuite API endpoints.
NetSuite API Endpoints
Here are the most commonly used NetSuite API endpoints:
Accounts
- GET /account
- POST /account
- DELETE /account/{id}
- GET /account/{id}
- PATCH /account/{id}
- PUT /account/{id}
Accounting Book
- GET /accountingBook
- POST /accountingBook
- DELETE /accountingBook/{id}
- GET /accountingBook/{id}
- PATCH /accountingBook/{id}
- PUT /accountingBook/{id}
Customers
- GET /customer
- POST /customer
- DELETE /customer/{id}
- GET /customer/{id}
- PATCH /customer/{id}
- PUT /customer/{id}
Vendors
- GET /vendor
- POST /vendor
- DELETE /vendor/{id}
- GET /vendor/{id}
- PATCH /vendor/{id}
- PUT /vendor/{id}
Transactions
- GET /transaction
- POST /transaction
- DELETE /transaction/{id}
- GET /transaction/{id}
- PATCH /transaction/{id}
- PUT /transaction/{id}
Items
- GET /item
- POST /item
- DELETE /item/{id}
- GET /item/{id}
- PATCH /item/{id}
- PUT /item/{id}
Employees
- GET /employee
- POST /employee
- DELETE /employee/{id}
- GET /employee/{id}
- PATCH /employee/{id}
- PUT /employee/{id}
Sales Orders
- GET /salesOrder
- POST /salesOrder
- DELETE /salesOrder/{id}
- GET /salesOrder/{id}
- PATCH /salesOrder/{id}
- PUT /salesOrder/{id}
Purchase Orders
- GET /purchaseOrder
- POST /purchaseOrder
- DELETE /purchaseOrder/{id}
- GET /purchaseOrder/{id}
- PATCH /purchaseOrder/{id}
- PUT /purchaseOrder/{id}
Invoices
- GET /invoice
- POST /invoice
- DELETE /invoice/{id}
- GET /invoice/{id}
- PATCH /invoice/{id}
- PUT /invoice/{id}
Payments
- GET /payment
- POST /payment
- DELETE /payment/{id}
- GET /payment/{id}
- PATCH /payment/{id}
- PUT /payment/{id}
Departments
- GET /department
- POST /department
- DELETE /department/{id}
- GET /department/{id}
- PATCH /department/{id}
- PUT /department/{id}
Locations
- GET /location
- POST /location
- DELETE /location/{id}
- GET /location/{id}
- PATCH /location/{id}
- PUT /location/{id}
Classes
- GET /classification
- POST /classification
- DELETE /classification/{id}
- GET /classification/{id}
- PATCH /classification/{id}
- PUT /classification/{id}
Currencies
- GET /currency
- POST /currency
- DELETE /currency/{id}
- GET /currency/{id}
- PATCH /currency/{id}
- PUT /currency/{id}
Tax Codes
- GET /taxCode
- POST /taxCode
- DELETE /taxCode/{id}
- GET /taxCode/{id}
- PATCH /taxCode/{id}
- PUT /taxCode/{id}
Subsidiaries
- GET /subsidiary
- POST /subsidiary
- DELETE /subsidiary/{id}
- GET /subsidiary/{id}
- PATCH /subsidiary/{id}
- PUT /subsidiary/{id}
Budget
- GET /budget
- POST /budget
- DELETE /budget/{id}
- GET /budget/{id}
- PATCH /budget/{id}
- PUT /budget/{id}
Expense Reports
- GET /expenseReport
- POST /expenseReport
- DELETE /expenseReport/{id}
- GET /expenseReport/{id}
- PATCH /expenseReport/{id}
- PUT /expenseReport/{id}
Time Entries
- GET /timeEntry
- POST /timeEntry
- DELETE /timeEntry/{id}
- GET /timeEntry/{id}
- PATCH /timeEntry/{id}
- PUT /timeEntry/{id}
Projects
- GET /project
- POST /project
- DELETE /project/{id}
- GET /project/{id}
- PATCH /project/{id}
- PUT /project/{id}
Work Orders
- GET /workOrder
- POST /workOrder
- DELETE /workOrder/{id}
- GET /workOrder/{id}
- PATCH /workOrder/{id}
- PUT /workOrder/{id}
Here’s a detailed reference to all the NetSuite API Endpoints.
NetSuite API FAQs
Here are the frequently asked questions about NetSuite APIs to help you get started:
What is the API limit for NetSuite?
NetSuite enforces concurrency limits rather than per-minute rate limits. Standard licences allow 10 concurrent web service requests; larger enterprise accounts may have higher limits. Exceeding the concurrency limit returns an EXCEEDED_CONCURRENCY_LIMIT_BY_INTEGRATION fault. SuiteQL REST API calls paginate at 1,000 rows per response — use the nextPageId parameter for larger datasets. Best practice is exponential backoff and request queuing rather than parallel firing.
How do I authenticate with the NetSuite API?
NetSuite supports two authentication methods: Token-Based Authentication (TBA) for server-to-server integrations, and OAuth 2.0 (available from NetSuite 2022.2+) for user-facing flows. TBA requires a manually constructed HMAC-SHA256 signed Authorization header on every request — including realm, oauth_consumer_key, oauth_token, oauth_signature_method, oauth_timestamp, oauth_nonce, and oauth_signature. Basic authentication was fully deprecated. Knit handles TBA signature construction and token lifecycle management automatically.
What is the difference between NetSuite REST and SOAP APIs?
The NetSuite REST API (SuiteQL) uses JSON payloads and is the recommended interface for new integrations — it supports SQL-like queries via POST to /services/rest/query/v1/suiteql. The SOAP API (SuiteTalk) uses XML and is the legacy interface, offering broader record coverage for complex transactions but slower to work with. New integrations should use the REST API unless the required record type is only available via SOAP.
Does NetSuite support webhooks?
NetSuite does not support native outbound webhooks. Real-time event notifications require either SuiteScript User Event scripts (server-side JavaScript that fires HTTP calls when records change) or Workflow Event Actions triggered by business process events. Most integrations use scheduled polling via SuiteQL with a lastmodifieddate filter. Knit provides virtual webhooks for NetSuite — subscribe to normalised change events and Knit handles polling, deduplication, and delivery.
What is SuiteScript?
SuiteScript is NetSuite's JavaScript-based API for custom business logic that runs server-side inside NetSuite. It supports User Event scripts (triggered by record creates/edits), Scheduled scripts (run on a timer), Client scripts (run in the browser UI), and RESTlets (custom REST endpoints hosted in NetSuite). SuiteScript is used for automation and write operations; SuiteQL is used for read operations from outside NetSuite.
Find more FAQs here.
Get started with NetSuite API
To access NetSuite APIs, enable API access in NetSuite, create an integration record to obtain consumer credentials, configure token-based authentication (TBA) or OAuth 2.0, generate access tokens, and use them to authenticate requests to NetSuite API endpoints.
However, if you want to integrate with multiple CRM, Accounting or ERP APIs quickly, you can get started with Knit, one API for all top integrations.
To sign up for free, click here. To check the pricing, see our pricing page.
.png)
.png)
.png)
.webp)
