-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unauthorized Error 401. Tried to regenerate tokens but still issue persists #69
Comments
Have you set the correct environment variables? Which sample are you running? |
Yes - to follow up. Same thing happening to me intermittently. Not sure if it is the control c exit not working properly in node.js, but once it quits on a timeout, it gives me a 401 error when i re open. |
I do have same error. Making a recent searce with axios (Js) and header contains a bearer token which keeps responding Unauthorized. tried using it on Postman too with the same error. I have regenerated to no avail. |
I am having the same problem running the sample code "Filtered-Stream" with either needle or axios with node.js. |
|
It is part of v2 access and so far I have Essential account. |
I keep getting the same error, both using Python and Postman.. |
this case it's still open , omg why ? |
401 [Done] exited with code=1 in 2.356 seconds |
me 22222. Why no one helps us ...lol |
I am using python sample code provided in the repository. But I am getting "builtins.Exception: (401, '{\n "title": "Unauthorized",\n "type": "about:blank",\n "status": 401,\n "detail": "Unauthorized"\n}')" error whenever I try to fetch data using any Endpoint. I tried to regenerate tokens with Read, Write Permissions but still the issue persists.
The text was updated successfully, but these errors were encountered: