Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> The redirect_url given in Airbyte is `localhost:3000/auth_flow`. Etsy won't be able to reach localhost as it requires public URL.
How to fix this? Is it possible to complete OAuth 2.0 flow for Etsy API  in Airbyte?

Etsy indeed can’t call back to `localhost:3000/auth_flow`, but that’s not actually required for Airbyte’s OAuth to work.  From the docs, OAuth redirects “happen in your web browser, not the Airbyte server,” and OAuth is explicitly supported even for air‑gapped/self‑managed instances.[\[Using OAuth\]](<https://docs.airbyte.com/platform/using-airbyte/oauth>)[\[OAuth 1.8\]](<https://docs.airbyte.com/platform/1.8/using-airbyte/oauth>) That means:  - The browser is what needs to reach the redirect URL; Etsy does not need to reach your local network directly. - You configure the **redirect URI in Etsy** to match what Airbyte shows in the UI for that connector’s OAuth flow. - When you click “Authenticate” in Airbyte, your browser goes to Etsy, you grant consent, and Etsy redirects back to the Airbyte redirect URL in your browser.  So:  1. In Etsy’s app settings, set the redirect/callback URL to **exactly** the value that Airbyte shows when configuring the source (the UI shows the URI you must register with the provider).[\[Using OAuth\]](<https://docs.airbyte.com/platform/using-airbyte/oauth>) 2. Make sure you are accessing Airbyte via the same hostname/port as in that redirect URL (e.g., if it’s `<http://localhost:3000/auth_flow>`, you should be using Airbyte at `<http://localhost:3000>` from the same browser). 3. Then run the OAuth flow from the Airbyte UI.  The knowledge sources do not provide Etsy‑specific examples, but they do confirm that OAuth works in self‑managed/local setups and that the key requirement is a matching redirect URI, not public reachability from the provider to your machine.[\[Using OAuth\]](<https://docs.airbyte.com/platform/using-airbyte/oauth>)

Yes, it’s possible to complete OAuth 2.0 for a local/self‑managed Airbyte instance, even though the redirect URL looks like `localhost:3000/auth_flow`.  Key points from the docs:  - In self‑managed setups you **must bring your own OAuth client** (client ID/secret).[[Using OAuth](<https://docs.airbyte.com/platform/using-airbyte/oauth>)] - OAuth **is supported in airgapped/local instances** because *redirects happen in your web browser, not the Airbyte server*.[[Using OAuth](<https://docs.airbyte.com/platform/using-airbyte/oauth>)] - The critical requirement is that the **redirect URI you register in Etsy exactly matches the one shown by Airbyte’s UI** for that connector.[[Using OAuth](<https://docs.airbyte.com/platform/using-airbyte/oauth>)]  What this means in practice:  1. In the Etsy app configuration, set the redirect/callback URL to exactly the URI Airbyte shows (e.g., `<http://localhost:3000/auth_flow>` or whatever Airbyte displays for that connector). 2. Open and use Airbyte from the same base URL in your browser (e.g., `<http://localhost:3000>` if that’s what the redirect uses). 3. Start the OAuth flow from the Airbyte UI; Etsy will redirect **your browser** back to that URL. Etsy does not need to “call into” your network outside this browser redirect.  The knowledge sources do not mention Etsy specifically or any Etsy‑specific quirks, so if Etsy imposes extra constraints beyond a standard OAuth 2.0 redirect, that is not covered in the docs.