Netsuite community connector

[assaf-cloudinary]

Hi,
I went through the entire documentation on this and defined everything mentioned there.
When trying to set upp the connection - the testing fails on this error:

Configuration check failed
HTTPError('400 Client Error: Bad Request for url: https://xxxxxxx.suitetalk.api.netsuite.com/services/rest/record/v1/contact?limit=1')

any ideas?

[Airbyte Support Bot (airbyte-support-bot)]

Hi assaf-cloudinary, thank you for reporting this!

We're looking into the 400 Bad Request error you're seeing during connection setup. This error typically occurs when the NetSuite REST API rejects the request, which can happen for a few common configuration reasons.

Troubleshooting Steps

1. Verify REST Web Services is enabled

• Go to Setup » Company » Enable Features » SuiteCloud tab
• Scroll to SuiteTalk (Web Services) and ensure REST WEB SERVICES is checked
• Also confirm CLIENT SUITESCRIPT, SERVER SUITESCRIPT, and TOKEN-BASED AUTHENTICATION are enabled

2. Verify your role has permissions to access Contact records

• Go to Setup » Users/Roles » Manage Roles and edit the role assigned to your integration
• Under the Permissions tab, ensure the Lists section includes the Contacts permission with at least View access
• Also confirm that Transactions, Reports, Lists, and Setup sections all have the required permissions as described in the setup guide

3. Check your Realm (Account ID) format

• The Realm should be your Account ID (e.g., 5319463 for production, or 5319463_SB2 for sandbox)
• You can verify this under Setup » Company » Company Information

4. Verify the integration record is active

• Go to Setup » Integration » Manage Integrations
• Ensure the integration you created has State set to Enabled

5. Try specifying object types

• If the default Contact check keeps failing, try adding specific object types in the connector configuration to test with a different record type that your role definitely has access to

Could you share the following details (please make sure to mask or remove any sensitive information such as API keys, passwords, tokens, or connection strings):

• Which version of Airbyte are you using (OSS or Cloud)? If OSS, which version?
• The connector version you're using
• Whether you've verified all the SuiteCloud features are enabled (REST Web Services, Token-Based Authentication)
• The permissions assigned to the role used for the integration

We've escalated this to our team for further investigation.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[Airbyte Support Bot (airbyte-support-bot)]

This issue is being tracked internally: https://github.com/airbytehq/oncall/issues/12957

[assaf-cloudinary]

didn't work, i'm suspecting the permissions - probably something we missed. can I get the full list of permissions needed for this integration?

[Anubhav Singh (UnknownHawkins)]

The user reports a 400 Bad Request when testing NetSuite connection via community connector. They suspect permissions. Must not repeat existing replies. Must not self-promote. Should give answer: list of permissions required, maybe mention role needs "Full" or specific privileges: "Customer Center", "Web Services", "RESTlet", "SuiteTalk", "Record/Contact" read, also need to enable "Client Center" and "Web Services" and "RESTlet" and "SuiteTalk". Also need to ensure "Enable RESTlet" and "Enable SuiteTalk". Also need correct token, consumer key/secret, token secret, etc. Provide troubleshooting steps: ensure the role has "Full" or "Customer Center" and "Web Services" and "SuiteTalk" permissions, also check that the user has "Search" and "Use" on Contact. Also ensure correct account ID and endpoint. Provide answer directly.". Actually "If" is allowed? Only opening with "I" is prohibited.