The API Report CardAPI Index
Airbyte

Airbyte API

airbyte.com

Airbyte ships a documented public REST API for Cloud and self-managed deployments, covering connector CRUD and job control. Access is self-serve: create a client ID and secret in the UI and exchange them for short-lived bearer tokens. Fixed rate limits are unpublished; throttling surfaces as 429s.

Last verified: July 2026Software & Data Tools
API GRADE
A+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST API at api.airbyte.com/v1 with a maintained OpenAPI spec; the same surface ships on self-managed deployments.
AccessGOODSelf-serve: create a client ID and secret in the Airbyte UI, then exchange them for bearer tokens. No approval gate.
CoverageGOODSources, destinations, connections, and jobs get full CRUD plus trigger-sync and job polling; batch semantics, not per-record events.
AuthGOODClient-credentials grant issuing short-lived bearer tokens; teams must handle refresh and 401 retries themselves.
Docs & DXGOODOfficial Python SDK, PyAirbyte, a Terraform provider, an MCP server, and a public OpenAPI spec for generating clients.
StabilityGOODStable v1 surface with a public OpenAPI spec; rate limits are fair-use, surfacing as 429s with backoff guidance.
Supergood: Airbyte shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Airbyte scores A+ on the API Report Card. Airbyte ships a documented public REST API for Cloud and self-managed deployments, covering connector CRUD and job control. Access is self-serve: create a client ID and secret in the UI and exchange them for short-lived bearer tokens. Fixed rate limits are unpublished; throttling surfaces as 429s.

Tried to integrate with Airbyte?
SOURCES
Access tokens are short-lived and must be refreshed frequently; teams must implement caching + 401-retry logic themselves rather than relying on a long-lived API key docs.airbyte.com
No publicly documented rate-limit numbers, customers report having to discover throttling empirically via 429s docs.airbyte.com
Self-managed deployments require passing workspace ID on every request, adding friction vs. Cloud docs.airbyte.com
OAuth-app management is global rather than per-workspace, blocking multi-tenant patterns; long-standing community request github.com
Schema-drift / discover-schema failures surface as opaque API errors that don't pinpoint the offending stream or column g2.com
The API exposes batch/job semantics (trigger-sync, poll-job) rather than per-record event semantics; not suited to low-latency event-driven workflows without pairing with the streaming/CDC path reference.airbyte.com
Cloud API base URL differs from self-managed (`api.airbyte.com/v1` vs `/api/public/v1`), forcing client code branching for hybrid deployments docs.airbyte.com
Embedded / Powered-by-Airbyte API is documented separately from the core API, complicating discovery for SaaS-vendor adopters airbyte.com
Connector versioning is exposed in the API but breaking-change semantics across connector major versions are under-documented docs.airbyte.com
Long-tail and less-popular connectors are reported as buggy; sync failures with cryptic, opaque error messages are the most-cited operational pain g2.com
Schema-drift handling during CDC (e.g., MSSQL to Snowflake) causes pipeline failures and 'Discovering schema failed' errors tied to primary-key inconsistencies g2.com
Support response times are widely criticized; multiple reviewers cite slow turnaround on broken-connector tickets as a reason for migrating away trustradius.com
Self-hosted Open Source edition has a difficult setup and ongoing operational burden (Kubernetes, Temporal, Postgres metadata DB) g2.com
Pricing is opaque on Cloud (volume-based) and capacity-based on Enterprise; users ask for a dedicated cost calculator and more predictable bills g2.com
Handling very large initial syncs frequently requires manual tuning to avoid Temporal/worker timeouts g2.com
Historical OAuth UX required developer-level effort to extract refresh tokens (~1 hour per integration) before platform improvements github.com
Per-workspace OAuth-app override has been a long-standing customer ask in the OSS repo github.com