Hi all, I have a come across a weird scenario while the using the airbyte apis. I have installed airbyte using docker and I am trying to manage workspaces using the apis. However , the api POST http://localhost:8000/api/v1/workspaces/get (fetching a workspace by ID) always fetches one default (that was created originally while setting up airbyte) workspace even after passing a different workspace ID. The same thing happens with the delete workspace api also POST http://localhost:8000/api/v1/workspaces/delete . Any idea why these apis are ignoring the workspace ID passed in the body and always considering the default workspace ? Note that this default workspace is created when I first opened up the airbyte UI after installation.

Hi Ishan! Thanks for your patience - I was out last week for the holidays and am catching up with messages now. I don't think multiple workspaces are officially supported for OSS. Let me look into this and get back to you!

@Nataly Merezhuk (Airbyte) any news on this ? I am also trying to work another use case. I have created multiple workspaces through the airbyte apis and then I am trying to update the airbyte UI url with the new workspace Id to render data for the new workspace. But this also doesn't work. It always renders the default workspace ?

Hi Ishan, at this point multiple workspaces are available to OSS through the API but it's not a feature that's fully supported so it might have some bugs. They are not available in the UI. We don't have plans to make this a robust feature in OSS, unfortunately!

Multiple workspaces are no longer supported for the