This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Guessing I must be missing something obvious.  Changing the URLs to the SuiteQL ones keeps returning me error: "error="token_rejected", error_description="Invalid login attempt.""...  But my TBA credentials work perfectly fine with a RESTlet URL instead... :confused:

The initial RESTlet URL is:
<https://xxxxxx-sb1.restlets.api.netsuite.com/app/site/hosting/restlet.nl>

The REST web services URL I'm trying to switch it to is:
<https://xxxxxx-sb1.suitetalk.api.netsuite.com/services/rest/query/v1/suiteql?limit=5>

We are also using the correct URL
<https://XXXX-sb1.suitetalk.api.netsuite.com/services/rest/query/v1/suiteql?limit=1000&amp;offset=0>

Remember to set the header "Prefer: transient" and your OAuth authorization has to be perfect, but if it works for restlets; but not SuiteQL then maybe its the role rights?

Nah, not the role.  I able to connect without any issues using Postman.  Let me make sure that I've added the prefer header.

Yeah, still no luck.  My guess is that the way the signature is created.  The RESTlet one includes all the custom fields (query string).  For the REST API, I've tried doing the same, but still no luck.

so you are creating the signature manually? or using postman?

there are a lot of gotchas when you do it manually hah

Postman works fine.  When I try to replicate it manually, it fails.  Though it works fine for RESTlets, both ways... :confused:

do you have a code snippet of how you are generating the signature

For a recent Java-based integration, I ended up using the OAuthParameters class from Google. There are some code examples online to calculate the signature manually instead, I could dig one or two up if needed.

In c# I used an OAuth nuget library just to generate the correct signatures etc,.