Fivetran / Airbyte (metadata access)
Connecting to their metadata, not using them as connectors.
Access mode: Read-only
Required information
| Field | Details |
|---|---|
| Platform | Fivetran or Airbyte (Cloud or self-hosted). |
| Authentication | Fivetran: API key + secret. Airbyte: API token or basic auth. |
| Scope | Connector definitions, sync status, schema mappings. |
Network considerations
Fivetran: HTTPS to api.fivetran.com. No VPN needed.
Airbyte Cloud: HTTPS to api.airbyte.com. No VPN needed.
Airbyte self-hosted: Standard networking. API default on port 8001.
Credential and auth management
Fivetran: API key + secret. Generated in Fivetran dashboard (Settings → API Config). Read-only by default.
Airbyte Cloud: API token. Generated in Airbyte Cloud settings.
Airbyte self-hosted: Basic auth. Default credentials or OIDC if configured.
Purpose: Understanding what data Fivetran/Airbyte replicates, from where, to where, and on what schedule. This feeds lineage without duplicating their connectors.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Fivetran auth | GET /v1/connectors | Lists connectors |
| Fivetran schema | GET /v1/connectors/<id>/schemas | Returns schema mapping |
| Airbyte auth | GET /v1/sources | Lists sources |
| Airbyte connections | GET /v1/connections | Lists connections with stream mappings |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.