Lucas Miura
06/24/2026, 7:22 PMkapa.ai
06/24/2026, 7:22 PMPOST /connections), the knowledge sources do not explicitly describe whether a discover (schema detection) step is automatically triggered as part of that API call itself.
However, here's what the knowledge sources do tell us:
• Schema discovery happens at connection setup time in the UI — when a user configures a connection, Airbyte runs a discover step to determine the schema for each stream. [APIs with variable schemas]
• There is a separate API endpoint specifically for triggering schema discovery: POST /v1/sources/discover_schema. This suggests that schema discovery is not necessarily bundled into the connection creation call, but can be triggered independently. [Forum: Trigger schema detection]
• Schema discovery also runs before each sync — for Cloud users, Airbyte checks for schema changes immediately before syncing (at most every 15 minutes), and for self-managed users, at most every 24 hours. [Schema change management]
• The GitHub issue about DISCOVER_REFRESH_WINDOW_MINUTES also confirms that discover runs as part of the sync workflow, not necessarily at connection creation time. [GitHub Issue: Discover Behavior]
In summary: The knowledge sources suggest that when creating a connection via the API, you likely need to call POST /v1/sources/discover_schema separately to trigger schema discovery, rather than it being automatically included in the POST /connections call. The discover step appears to be most reliably triggered either manually via its dedicated endpoint, or automatically before syncs run.
That said, the knowledge sources don't explicitly confirm the exact behavior of POST /connections with respect to auto-triggering discover, so I'd recommend consulting the Airbyte API reference or testing directly to confirm. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.