I checked the API and the connection creation endpoint doesn't let user to define the schemas of the streams: https://reference.airbyte.com/reference/createconnection but you can do it in the Config API. I checked "Powered by Airbyte" and for now only the headless mode is supported. But - as per my thread on https://airbytehq.slack.com/archives/C039Y6EGTGV/p1687955853212469 - if we can't define schemas per stream, what would happen if we send a liststreams with ignoreCache = false? It will detect schema changes, but the API only let us ignore schema changes or disable a connection. As I mentioned in that thread, using the UI to change how a connection handles the schema changes is not an option for us.

Hey @Luis Vicente - our team just discussed this, and we have some space in our current sprint to add to the Airbyte API - the new modes for handling schema changes (propagate all changes & propagate column changes only). We have heard similar feedback from other API users. Our target would be to have this available for use at the end of next week (july 7) or early in the week following. If we made that addition to the Airbyte API, would that unblock your use case?

Yes, that would be give us a clean solution for this use case.

Sounds good. As mentioned, we will be working on this next week, and should have it available on july 7th, or in the week following. We will circle back to this thread when it is ready to use.

Thanks!