Skip to content
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

Closed
philiprcleary opened this issue Apr 26, 2024 · 3 comments
Closed

[Bug]: Api Not authenticated #2500

philiprcleary opened this issue Apr 26, 2024 · 3 comments
Labels
area: backend Related to backend functionality or under the /backend directory area: docs Related to documentation or under the /docs directory bug Something isn't working Stale

Comments

@philiprcleary
Copy link

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

@philiprcleary philiprcleary added the bug Something isn't working label Apr 26, 2024
Copy link

dosubot bot commented Apr 26, 2024

To interact with the quivr API and authenticate your requests, you'll need to include an authorization header in the format Authorization: Bearer YOUR_ACCESS_TOKEN. Here's a quick guide to help you with the authentication process:

  1. Obtaining an Access Token: You need a valid JWT token or API key. If you're unsure how to obtain this, it typically involves logging into the quivr platform or contacting their support to generate an API key or token for your account.

  2. Using the Access Token: With your token, make API requests by adding the header Authorization: Bearer YOUR_ACCESS_TOKEN. Replace YOUR_ACCESS_TOKEN with your actual token.

  3. Handling Authentication in Code: The quivr API uses a Bearer authentication method. If you're working with the API programmatically, ensure your requests include the correct authorization header. For development or testing, if the AUTHENTICATE environment variable is set to "false", authentication can be bypassed, simulating a test user.

  4. Documentation and API Keys: If the API documentation seems missing, it's now located at https://api.quivr.app/openapi.json. For API keys, if you need to retrieve or manage your keys, this typically involves accessing your user settings or dashboard within the quivr platform.

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!

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

@dosubot dosubot bot added area: backend Related to backend functionality or under the /backend directory area: docs Related to documentation or under the /docs directory labels Apr 26, 2024
@StanGirard
Copy link
Collaborator

Hey!

You need to create an api key from the frontend in the user page :)

The documentation is here: https://api.quivr.app/docs

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Jul 26, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: backend Related to backend functionality or under the /backend directory area: docs Related to documentation or under the /docs directory bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

2 participants