-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Bug]: Api Not authenticated #2500
Comments
To interact with the quivr API and authenticate your requests, you'll need to include an authorization header in the format
If you encounter "No authenticated" errors, double-check that your token is correctly included in the request headers and is valid. For any issues related to lost or managing API keys, the quivr platform's user settings or support would be the next steps to resolve those concerns. This should cover the essentials for authenticating with the quivr API and getting started with your requests. If there's anything more specific you need help with, feel free to ask!
|
Hey! You need to create an api key from the frontend in the user page :) The documentation is here: https://api.quivr.app/docs |
Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion. |
What happened?
I am trying to interact with quivr via the api endpoint but I can't find how to get the access token. Every request understandably returns "No authenticated". Also, the api documentation has been removed from the docs. Why?
Relevant log output
No response
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: