Berke Eruz
03/22/2026, 5:55 PMkapa.ai
03/22/2026, 5:56 PMclient_id and client_secret.
3. Exchange them for an access token by making a POST request to your Airbyte instance:
curl --request POST \
--url <YOUR_AIRBYTE_URL>/api/v1/applications/token \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{
"client_id": "<YOUR_CLIENT_ID>",
"client_secret": "<YOUR_CLIENT_SECRET>"
}'
Replace YOUR_AIRBYTE_URL with the URL you use to access your Airbyte UI (e.g., http://localhost:8000 if running locally). [configuring API access]
The response will include an access_token (Bearer Token) that you can use in your Airflow DAGs to trigger Airbyte syncs via the API. Note that access tokens are short-lived (3 minutes for self-managed), so you should fetch a new token before each request. [1.8 API access] š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Berke Eruz
03/22/2026, 6:00 PMkapa.ai
03/22/2026, 6:01 PMabctl, you can also retrieve your credentials via the command line: abctl local credentials ā though some users have reported this doesn't always work for token generation. [configuring API access]
If neither option works, this may be a UI bug in your specific version. The knowledge sources don't provide a definitive fix for this, so I'd recommend checking the Airbyte GitHub issues or reaching out to the Airbyte community for version-specific support. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Berke Eruz
03/22/2026, 6:05 PMkapa.ai
03/22/2026, 6:05 PMclient_id and client_secret) directly from the Kubernetes secret rather than through the UI:
kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml
This will return something like:
apiVersion: v1
data:
instance-admin-client-id: Y2Q1ZTc4ZWEtMzkwNy00ZThmLWE1ZWMtMjIyNGVhZTFiYzcw
instance-admin-client-secret: cmhvQkhCODlMRmh1REdXMWt3REpHZTJMaUd3N3c2MjU=
instance-admin-password: d0V2bklvZEo1QUNHQnpPRWxrOWNSeHdFUGpJMWVzMWg=
The values are base64 encoded. To decode them, run:
echo '<YOUR_BASE64_VALUE>' | base64 -d
[authentication docs]
Once you have your client_id and client_secret, you can exchange them for an access token:
curl --request POST \
--url <YOUR_AIRBYTE_URL>/api/v1/applications/token \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{
"client_id": "<YOUR_CLIENT_ID>",
"client_secret": "<YOUR_CLIENT_SECRET>"
}'
[2.0 API access]
The knowledge sources don't explicitly explain why the "User settings" / "Applications" section may be missing from your Helm-deployed UI. This could be a UI bug or a version-specific issue. If the above workaround doesn't resolve your situation, I'd recommend checking the Airbyte GitHub issues for your specific version. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.