You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the cloud version of Flowise.
I have generated an ApiKey from the Flowise menu to access the API with a simple GET request (list existing chatflows in account).
I added this key in authentication header of my request. I got response from Api as expected.
But after some period of inactivity I got error "401-Unauthorized" and suggestion to go to flowise.com/auth/login
When I login to Flowise with web browser, then ApiKey become valid again.
To Reproduce
Go to "API Keys" menu. Generate new key or use Default
Use this key to send request curl --request GET \ --url https://<sample>.flowiseai.com/api/v1/chatflows \ --header 'Authorization: <generated key>'
Make sure you have the correct expected result
Wait for 1-2 days (do not login or use account this time)
Expected behavior
ApiKey will not expire, or it will be possible to login again with an http post request (flowise.com/auth/login endpoint requires web browser).
Screenshots
Setup
Cloud version at flowise.com
Flowise Version 2.2.1
Browser chrome/cURL
The text was updated successfully, but these errors were encountered:
I am using the cloud version of Flowise.
I have generated an ApiKey from the Flowise menu to access the API with a simple GET request (list existing chatflows in account).
I added this key in authentication header of my request. I got response from Api as expected.
But after some period of inactivity I got error "401-Unauthorized" and suggestion to go to
flowise.com/auth/login
When I login to Flowise with web browser, then ApiKey become valid again.
To Reproduce
curl --request GET \ --url https://<sample>.flowiseai.com/api/v1/chatflows \ --header 'Authorization: <generated key>'
Expected behavior
ApiKey will not expire, or it will be possible to login again with an http post request (
flowise.com/auth/login
endpoint requires web browser).Screenshots
Setup
The text was updated successfully, but these errors were encountered: