Reference · built on requestConnectorStreams, queues & webhooks

Airbyte

Connections, sync jobs, and job status from Airbyte Cloud or Self-Managed, with syncs started and cancelled through the Airbyte API.

Request accessPricing ↗

About

Airbyte is a data movement platform offered as Airbyte Cloud and as Self-Managed Enterprise and Community editions. A connection links one source to one destination, carries a stream list with a syncMode per stream, and runs on a manual, basic, or cron schedule. The Airbyte API at api.airbyte.com lists workspaces, sources, destinations, and connections, starts a sync or reset job, and reports each job's status, duration, bytesSynced, and rowsSynced. Workspace notifications post failed syncs, successful syncs, and connection updates to a webhook URL.

Through Fibric, an operator watches job outcomes and proposes a sync, a cancel, or a connection status change. You approve, and the connector records the job it started.

This is a reference listing. It documents what Fibric would read from Airbyte and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Connections from GET /connections with status active, inactive, or deprecated, schedule.scheduleType of manual, cron, or basic, dataResidency, and createdAt
  • Each connection's configurations.streams with a syncMode of full_refresh_overwrite, full_refresh_append, incremental_append, or incremental_deduped_history
  • Jobs from GET /jobs filtered by connectionId, jobType, status, workspaceIds, and createdAt or updatedAt windows
  • A job's status of pending, running, incomplete, failed, succeeded, or cancelled, with startTime, duration, bytesSynced, and rowsSynced
  • Workspace notification webhooks for Failed syncs, Successful syncs, Connection Updates, and Connection Updates Requiring Action
  • The Warning - Repeated Failures notice before a connection is disabled, and Sync Disabled - Repeated Failures once it is

Proposed actions

  • Target capability: propose starting a sync or reset job for a connection with POST /jobs
  • Target capability: propose cancelling a running job with DELETE /jobs/{jobId}
  • Target capability: propose setting a connection inactive or active, or changing its schedule, with PATCH /connections/{connectionId}
  • Target capability: propose a change to a connection's stream list or nonBreakingSchemaUpdatesBehavior, sent as a full overwrite of the stream configuration

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Restart a sync after a source outage

    A Failed syncs notification lands. The operator checks the latest job status, waits for the source to answer, and proposes a new sync job. You approve once, and the receipt names the jobId.

    With Webhook Replay, Integration Health

  • Notice the table that stopped moving

    The operator compares each connection's last succeeded job against its schedule and flags the ones with no succeeded job inside the expected window.

    With Data Freshness

  • Cancel a runaway job before it blocks the queue

    A job has been running far past its usual duration. The operator proposes DELETE /jobs/{jobId}, and a fresh sync once the cause is fixed.

    With Integration Health, Quota Headroom

Requirements

  • An Airbyte Cloud workspace or a Self-Managed Enterprise or Community deployment reachable from the connector
  • An Application created under Settings, Account, Applications; its permissions follow the user who created it
  • Workspace IDs for the connections in scope; an empty workspaceIds list returns every workspace the application can see
  • For notifications, a webhook URL set under Workspace settings, Notifications for each event type you want posted
Authentication
An Airbyte Application's Client ID and Client Secret, exchanged at /v1/applications/token for a Bearer access token that is valid for 3 minutes on Airbyte Cloud.

Limits

  • Access tokens last 3 minutes on Airbyte Cloud and 24 hours on Self-Managed Enterprise, so the connector fetches a fresh token before each request
  • List endpoints return 20 items by default and at most 100 per page, with offset paging
  • A stream configuration sent with PATCH /connections replaces the whole existing stream configuration, so the connector must send the full list
  • Self-Managed Community allows a single Application. Email notifications are available on Airbyte Cloud only

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Airbyte ↗

Questions and answers

How does the Airbyte API authenticate?
You create an Application under Settings, Account, Applications and receive a Client ID and Client Secret. Exchanging them at /v1/applications/token returns a Bearer access token. On Airbyte Cloud the token lasts 3 minutes; on Self-Managed Enterprise, 24 hours. The application carries the permissions of the user who created it.
Which job types can the API start?
POST /jobs takes a connectionId and a jobType of sync or reset. The response reports jobId, status, startTime, and, once known, duration, bytesSynced, and rowsSynced. Status moves through pending, running, incomplete, failed, succeeded, or cancelled. DELETE /jobs/{jobId} cancels a job.
Does Airbyte send webhooks when a sync fails?
Yes, through workspace notifications. Under Workspace settings, Notifications you can enable Failed syncs, Successful syncs, Connection Updates, Connection Updates Requiring Action, and the repeated-failure and upgrade warnings for a webhook URL. Webhooks work on Cloud and Self-Managed; email notifications are Cloud only.
Ask about Airbyte

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Airbyte through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy