API documentation

Airbyte has 2 APIs. Please see the table below for differences between them.

Configuration API	Airbyte API
Purpose: Enables OSS users to configure their own Self-Hosted Airbyte deployment (ex UI, internal state, etc)	Purpose: Enables users to control Airbyte programmatically and use with Orchestration tools (ex: Airflow)
Purpose: Enables Airbyte team to configure Airbyte Cloud (ex UI, internal state, etc)	Purpose: Exists for Airbyte users to write applications against and enable Powered by Airbyte (Headless version and UI version)
Status: Alpha state and might change. You won’t lose any functionality, but you may need to update your code to catch up to any backwards incompatible changes in the API.	Status: Closed Beta. See Airbyte roadmap for more details.
Documentation Available here	Documentation: Available to Closed Beta participants.