Oracle NetSuite REST connector
The Oracle NetSuite REST connector allows running SuiteQL queries to perform actions like list, get, delete, update, upsert and create records using SuiteTalk REST web services.
API versions: V1
API types: REST
Authentication and Authorization: OAuth 2.0
Key capabilities: SuiteQL, Custom Field support, basic create, retrieve, update, and delete operations
Prerequisites:
- NetSuite account
- Working webMethods Integration tenant
Custom Actions
You can also create your own custom actions for performing specific tasks.
Learn more about how to create custom actions.
Usage notes
SuiteQL
-
By default, the select and from clauses are set to the selected fields and recordType respectively when creating the operation, unless explicitly overridden.
-
The complexQuery takes precedence when the specified and any query request inputs are disregarded.
-
The Add a Field option can be used when your query response includes fields that are not displayed on the field selection screen.
Get Record
-
The default values for fields are set to fields selected while creating the operation.
-
The default value for expandSubresource is set to false. However, to retrieve subresources in the response you can use the parameter expandSubresource.Note: When expandSubresource is used, any specified fields are ignored.
List Record
You can filter the collection of all record instances by specifying filter conditions. For more information about Record Collection Filtering, see the NetSuite Application Online help.
Other Operations
Using the create, update, and upsert operation, you can retrieve the Location header in a successful response that includes the ID of the affected record.
Limitations
-
Some recordTypes are labeled as beta, indicating that their functionality is preliminary and subject to change or discontinuation without prior notice.
-
The List Records resource retrieves HATEOAS links and record IDs as a response.
-
The REST query service does not support the Asynchronous request execution.
-
The SuiteQL resource retrieves the field values and does not support the retrieval of sublist, subresource or similar data.
-
The refresh token request returns both an access and a refresh token when using public clients with OAuth 2.0 authorization code grant flow. The refresh token can be used once and is valid for three hours.
-
The metadata-catalog call, which retrieves a list of recordTypes, might take longer due to delay in creating an operation.