The NetSuite REST web services provide an integration channel that extends the capabilities of SuiteTalk. REST web services provide a REST-based interface for interacting with NetSuite.
REST Web services is a new feature for the NetSuite integration. This is an easy method to implement and also REST is widely popular, REST Web services will be the future for the NetSuite Standard Integration.
Following are the NetSuite REST service features:
- Use CRUD (create, read, update, delete) operations to perform business processing on NetSuite records and to navigate dynamically between records
- Get and process the API definition and record metadata
- Execute NetSuite queries on records
REST enables us to have simple access to record meta data. REST is a standard API that enables the third-party application can use directly without any write, deploy and run scripts. For using the REST web services, we need to do authentication which will be TBA(Token Based Authentication). We also need to create an integration record and also a role and for the role need to create access tokens.
REST Web services can be tested using POSTMAN. NetSuite provides a postman collection for testing all the rest web services operations. We can import POSTMAN collection from NetSuite and so we can test each and every operation of NetSuite. NetSuite REST API environment will also be installed while we import the collection. The following image shows the POSTMAN collection that provided by the NetSuite
Some of the records cannot be fetched using REST Web Services these records are BETA. We can fetch Beta records via REST Web services by completing the Umbrella Beta Program Recruitment Form.
REST Web services also provide the Query operations. Here we can write the SQL language and based on that we can fetch data directly from the database which will have a faster response time. So some beta records can be fetched by doing queries and so we don’t need to complete the Umbrella Beta program.
REST Web services are very easy to set up so lots of integration can be done easily.
For REST Web services, refer Record Browser schema to find internal ids and available fields for the records.