Has anyone been able to communicate with RESTlets using the fetch library? I am specifically using fetch in a React application

ive used note-fetch serverside, but i wouldnt expect it to be reasonable to put credentials clientside

Here is my fetch code. Do you see anything wrong with it? fetch('https://5557777-sb2.restlets.api.netsuite.com/app/site/hosting/restlet.nl?script=5555&deploy=2', { method: 'GET', mode: 'no-cors', headers: { 'Authorization': 'NLAuth nlauth_account=account, nlauth_email=email, nlauth_signature=password, nlauth_role=3', 'Content-Type': 'application/json', 'User-Agent-x': 'SuiteScript_Call' } }) .then(response => {return response.json()}) .catch(error=>console.log(error))

im assuming you are getting cors errors

The react app is rendered by a Suitelet. So I thought that could work because I am using the React framework kinda like a client script. So you're saying there is no way to get past the cors errors?

if you send the request from an internal page (ie you have the jsessionid cookie)

Sorry, I guess I don't understand how this can be done with React.

whats the url of your suitelet

thats an internal url

So I cannot use a RESTlet url?

your restlet has 2 urls

So I got a 403 error. Here is my code. fetch('https://555777-sb2.app.netsuite.com/app/site/hosting/restlet.nl?script=5577&deploy=2', { method: 'GET', headers: { 'Authorization': 'NLAuth nlauth_account=account, nlauth_email=email, nlauth_signature=password, nlauth_role=3', 'Content-Type': 'application/json', 'User-Agent-x': 'SuiteScript_Call' } }) .then(response => {return response.json()}) .catch(error=>console.log(error))

Dont send authorization header

It worked! OMG you're the best