Trouble connecting RapidAPI with NetSuite SuiteScript

[RunningTiger]

I’m encountering problems while trying to integrate RapidAPI in NetSuite SuiteScript. Although I can successfully use the same API key when testing in Postman, it fails in NetSuite.

Here’s the code I’m using:

var apiHeaders = [
    {
        name: "x-rapidapi-host",
        value: "your-api-host"
    },
    {
        name: "x-rapidapi-key",
        value: "your-api-key"
    }
];

var responseData = https.request({
    method: https.Method.GET,
    url: "https://your-endpoint.url",
    headers: apiHeaders
});

The response I receive is:

400 Error: Invalid API key. For further information, check https:docs.rapidapi.com/docs/keys.

Since the API key has been verified to work in Postman, I’m curious if there are any peculiarities in how NetSuite processes these requests. Has anyone managed to successfully connect RapidAPI with SuiteScript?

[JessicaDream12]

I’ve hit this same problem with RapidAPI and SuiteScript. NetSuite’s weird about how it processes request headers internally. Switch your headers to object format instead of array:

var responseData = https.request({
    method: https.Method.GET,
    url: "https://your-endpoint.url",
    headers: {
        "x-rapidapi-host": "your-api-host",
        "x-rapidapi-key": "your-api-key",
        "Content-Type": "application/json"
    }
});

Also check your script’s got permissions for external HTTPS requests. That 400 error looks like an API key problem but it’s usually just headers being formatted wrong.

[Liam23]

add a content-type header – netsuite’s picky about that. also check if your api key has special characters that might get encoded differently than postman.

[Nova56]

Had the same issue a few months ago. The problem wasn’t the API key - it’s how NetSuite handles request encoding. Wrap your API key value in encodeURIComponent(). Characters that work fine in Postman get mangled by NetSuite’s processing. Also check that your NetSuite account has SuiteScript HTTP requests enabled in company preferences. Spent hours debugging before realizing our admin had blocked external API calls. One more thing - handle the response with responseData.body since NetSuite puts the actual content there, not in the main response object like other platforms.