Summary
The user is facing issues accessing the Airbyte API using the OSS version and needs clarification on the correct authentication format and URL format. They are also unsure about the availability of the OSS version of the Airbyte API.
Question
Hello everyone! I have a problem with acessing the Airbyte API using the OSS version. What is the correct format for authentication and the url format itself with the OSS version. I have been getting conflicting advice from documentation and the AI. Also, is the OSS version of the Airbyte API available or not, generally?
Thank you for your attention!
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["accessing-airbyte-api", "oss-version", "authentication-format", "url-format", "availability", "conflicting-advice"]
Which Airbyte version do you use?
https://reference.airbyte.com/reference/authentication
> Airbyte OSS Users
> If you use the Airbyte API in OSS, you can use the credentials set for your UI instance. To do this, you should use the Basic authentication, with the username and password separated by a colon and Base64 encoded […]
I checked on local installation of Airbyte 0.63.14 and Basic Auth for email and password that I have configured, and it worked fine for me.
I tested simple endpoint returning workspaces http://localhost:8000/api/public/v1/workspaces
Keep in mind that you might need /api/public prefix for endpoints in docs
https://reference.airbyte.com/reference/standalone-server-deprecation-and-migration-to-airbyte-server