Summary
User is facing issues with using an API key to call Airbyte endpoints, receiving a 401 error. Assistance is needed to resolve this.
Question
Hi,
i’m Jouneid (working as data engineer), actually I am working on airbyte, wanted to implement this in our organisation. so I am running this locally using docker, and I created a connection with source and destination and its working fine. Now I need assistance with API key to call Airbyte endpoints to list connection etc.
I created one API key using https://portal.airbyte.com/, but it gives me error 401.
Any help with the API key to call Airbyte endpoints will be appreciated.
Thank you
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
["api", "api-key", "authentication", "airbyte", "error-401"]
Are you running Airbyte opensource? I think you’d need to make your api keys in its web interface, not in the cloud Airbyte version.
i clone the following airbyte official repo https://github.com/airbytehq/airbyte and running it locally, and I am creating the API in https://portal.airbyte.com/.
On local I could not find any path or way to create API key and use it for local connection API calls
Yeah, I’ll ask what http://portal.airbyte.com|portal.airbyte.com thing is, but I’m pretty certain it has nothing to do with your local environment. I.e. API keys made for http://cloud.airbyte.com|cloud.airbyte.com are for different env.
http://portal.airbyte.com/ is where you can login using your google account (using same google account for airbyte) create you API key, and use it for API (now this is for local or cloud airbyte, this is not clear to me).
i am running docker airbyte locally, and I need a way to create API to call airbyte Endpoints locally
The API access is only available to Self-Managed Enterprise https://docs.airbyte.com/enterprise-setup/
To be clear, you can still use the API to manage connections and such on OSS, but it doesn’t support things like OAuth endpoints and you need to set up your own access controls. You can find details on connecting via port 8001 under the <Getting Started Deployments> section of the API docs.