keshav
04/10/2026, 6:58 AManalytics.readonly scope).
• Using that token, I create a GA4 source via Airbyte API.
• The source gets created successfully and also passes the connection test.
❌ Problem
When I try to create a connection (GA4 → Postgres):
In Airbyte UI → it gets stuck on “Fetching schema”
• Via API → it returns a 500 error
✅ What I’ve Verified
• OAuth flow is correct (I receive refresh_token, client_id, client_secret)
• GA4 API works — I can successfully run:
properties/{property_id}:runReport
User has proper access to the GA4 property
• Tried different property_ids formats:
• "494091909"
"properties/494091909"
• Tried wider date range (2024-01-01)
• Issue still persists
🤔 Observation
• If I create the same GA4 source using Airbyte UI OAuth, everything works fine
• Issue only happens when the source is created via API using my OAuth tokens
âť“ Question
Is there any difference in how Airbyte Cloud handles:
• OAuth credentials internally (UI vs API)?
• Schema discovery for GA4 sources?
• Required config fields that might not be obvious in API?
Or is this a known issue/limitation with the GA4 connector?
Any guidance would be super helpful 🙏
Thanks in advance!kapa.ai
04/10/2026, 6:59 AMMark Grivnin
04/10/2026, 9:44 PMauth_type field. When you create the source through the Airbyte UI, it automatically injects "auth_type": "Client" into the credentials object, but when you're calling the API directly you need to include it yourself. Let me know if that helps!