Kailash Bisht
04/09/2026, 11:24 AMkapa.ai
04/09/2026, 11:25 AMPOST /sources/initiateOAuth
Content-Type: application/json
Body (example):
{
"sourceType": "your_source_name",
"redirectUrl": "https://your-app.com/oauth/callback",
"workspaceId": "871d9b60-11d1-44cb-8c92-c246d53bf87e",
"oAuthInputConfiguration": {
"host": "test.snowflake.com"
}
}
This returns an object containing a redirect_url. Redirect your user to that URL so they can authenticate with the source’s identity provider. After successful login, the IdP redirects back to an Airbyte endpoint, which stores the access/refresh tokens as a secret and then redirects to your redirectUrl with a secret_id query parameter. [Public API OAuth] 2. Use the secret_id when configuring the source The docs you provided do not include the exact payload shape for creating/updating a source with that secret_id, so I cannot give a precise request body. The documented part is only that the secret_id “can be used to create a source with credentials in place of actual tokens.” [Public API OAuth]
Because the knowledge sources do not show a dedicated “re-authenticate source” endpoint or a full example of updating an existing source with a new secret_id, I cannot describe that step in more detail with certainty. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Kailash Bisht
04/09/2026, 11:27 AMkapa.ai
04/09/2026, 11:27 AM#ask-ai or #ask-community-for-troubleshooting. [Getting Support 2.0]
• GitHub Discussions: Post questions or ideas in the Airbyte GitHub Discussions forum. [Get support]
• Report issues: Open a GitHub issue if you’ve found a bug or doc problem. [Get support] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.