It’s fixed now! If you’re still facing this, just unsubscribe and then resubscribe again.

(Details: there was a problem with header names in RapidAPI platform, I’ve updated the header names but old account still might use problematic header names. Resubscribing will solve this problem)

i receive Parse Error every time. Do I get charged for these Error Calls?

Maybe there is something wrong with RapidAPI server.

I found this issue here:
https://github.com/nodejs/node/issues/27711

It seems like a TLS error.

$ node test.js
/xxx/test.js:14
if (error) throw new Error(error);
^

Error: Error: Parse Error: Invalid header token
at Request._callback (/xxx/test.js:14:20)
at self.callback (/xxx/node_modules/request/request.js:185:22)
at Request.emit (events.js:305:20)
at Request.onRequestError (/xxx/node_modules/request/request.js:881:8)
at ClientRequest.emit (events.js:305:20)
at TLSSocket.socketOnData (_http_client.js:477:9)
at TLSSocket.emit (events.js:305:20)
at addChunk (_stream_readable.js:341:12)
at readableAddChunk (_stream_readable.js:316:11)
at TLSSocket.Readable.push (_stream_readable.js:250:10)

Hello!
Are you facing Parse Error when testing with code or only in the website? There seems to be a glitch with rapidapi platform that’s causing it to show Parse Error in the website.