Helix Sending User Access and App Access Tokens Trouble

[Kaguva]

Hi!!
i have a little problems with Helix

I just send this on Node.js with

in this way
       if(true)//true=kraken; false=helix;
    			{
    				console.log("------Kraken------");
    				options = {
    				url: 'https://api.twitch.tv/kraken/',
    				method: 'GET',
    				headers: {
    				  'Authorization': 'OAuth ' + result.access_token
    				}
    			  };
    			}
    			else
    			{
    				console.log("------Helix------");
    				options = {
    				url: 'https://api.twitch.tv/helix/',
    				method: 'GET',
    				headers: {
    				  'Authorization': 'Bearer ' + result.access_token//,
    				  //'Client-ID': TWITCH_CLIENT_ID
    				}
    			  };
    			}

			  request(options, function (error, response, body) {
				if (response && response.statusCode == 200) {
					
					console.log("SUCCESS API");
					console.log(body);

Kraken results:
{ access_token: ‘jd0v8z2tyr4xwjxl1ldto4s2kjg3jz’,
expires_in: 5134838,
scope: [ ‘user:read:email’ ] }

Helix Results:
{“error”:“Not Found”,“status”:404,“message”:“”}

[BarryCarlyon]

There is no end point at https://api.twitch.tv/helix/

Also you just published a users access_token to the wild (which is bad)

The examples in the docs demonstrate how to send the header. In this case the helix example is to a non valid end point.

The full list of Helix endpoints is here https://dev.twitch.tv/docs/api/reference/