Airbyte API

Name: Airbyte API
Brand: Airbyte API
Availability: InStock

✓ Official Vendor SpecAnalyticsData Pipelinesbearer96 EndpointsREST

For Agents

Provision sources and destinations, create and run data sync connections, and trigger or cancel jobs across Airbyte deployments.

Install Jentic One Beta

Connect the Airbyte API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Airbyte API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Airbyte API.

Provision and update sources and destinations from any supported connector definition

Create connections that move data between a source and destination on a configured schedule

Trigger sync, refresh, or reset jobs and cancel them in flight

GET STARTED

Start building with Airbyte API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Airbyte API for, with concrete tasks.

★ Programmatic Pipeline Provisioning

Stand up new data pipelines from code rather than the UI - useful for spinning up customer-specific replicas in multi-tenant SaaS. Create a source via POST /sources, a destination via POST /destinations, then a connection via POST /connections, and trigger an initial sync via POST /jobs. The same flow works against Cloud, OSS, and Enterprise deployments.

Create a Postgres source named 'tenant_42_db', a Snowflake destination 'analytics_warehouse', then a connection between them with daily schedule and trigger an initial sync

Job Orchestration and Monitoring

Orchestrate Airbyte syncs from an external scheduler or workflow engine. POST /jobs triggers a sync, refresh, or reset, GET /jobs/{jobId} polls status, and DELETE /jobs/{jobId} cancels a stuck run. List recent jobs with GET /jobs filtered by connection or job type.

Trigger a sync job for connection conn_abc, poll the job status every 60 seconds, and cancel it if it runs longer than 30 minutes

Embedded Data Connectors

Let SaaS customers connect their own data sources without leaving your app. Use POST /config_templates/sources to pre-configure connector defaults, embed the Airbyte widget for OAuth-style source connection, and list resulting sources via GET /sources scoped to the customer's workspace.

Create a config template for a Stripe source with the API key field marked as user-supplied, then list all sources created from that template across workspaces

AI Agent Data Pipeline Operator

An AI agent operating Airbyte through Jentic can search for the right operation, load the input schema, and trigger or reconfigure a connection on demand. The bearer token stays in your Jentic One instance and only scoped Airbyte calls are exposed to the agent.

Search Jentic for 'trigger an airbyte sync', load the POST /jobs schema, and start a sync for connection conn_abc with jobType=sync

Key Endpoints

96 endpoints — airbyte is an open data movement platform for moving data from sources to destinations through configurable connectors.

METHOD

PATH

DESCRIPTION

POST

/applications/token

Get an access token

GET

/sources

List sources

POST

/sources

Create a source

GET

/destinations

List destinations

POST

/destinations

Create a destination

POST

/connections

Create a connection

POST

/jobs

Trigger a sync, refresh, or reset job

GET

/jobs/{jobId}

Get job status and details

POST

/applications/token

Get an access token

GET

/sources

List sources

POST

/sources

Create a source

GET

/destinations

List destinations

POST

/destinations

Create a destination

POST

/connections

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Airbyte client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'trigger an airbyte sync', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without learning the full endpoint surface.

Time to first call

FAQs

Specific to using Airbyte API through Jentic.

What authentication does the Airbyte API use?

Airbyte uses bearer access tokens obtained from POST /applications/token by exchanging client credentials. Jentic stores the credentials encrypted in the vault, refreshes the token automatically, and never exposes the raw secret to the agent.

Can I trigger a sync job with the Airbyte API?

Yes. POST /jobs accepts a connectionId and jobType (sync, reset, or refresh) and returns a jobId you can poll with GET /jobs/{jobId}. To cancel a running job, use DELETE /jobs/{jobId}.

What are the rate limits for the Airbyte API?

Public rate limits are not declared in the spec; Airbyte Cloud throttles per workspace. For high-frequency polling, prefer webhooks or longer poll intervals on GET /jobs/{jobId} rather than tight loops.

How do I create a new source with the Airbyte API through Jentic?

Run pip install jentic, search Jentic for 'create an airbyte source', load the schema for POST /sources, then execute with the workspaceId, sourceDefinitionId, and connection configuration. Jentic injects the bearer token automatically.

Does the Airbyte API work against self-hosted OSS deployments?

Yes. The same v1 API surface is exposed by Airbyte Cloud, Enterprise, and OSS - only the base URL changes. Point the base URL at your OSS deployment and use the same operations to manage sources, destinations, and connections.

Can I list available connector definitions before creating a source?

Yes. GET /sources/definitions and GET /destinations/definitions return the catalog of connectors. Use these to discover the sourceDefinitionId or destinationDefinitionId required by POST /sources or POST /destinations.

Can I limit what my agent is allowed to do with the Airbyte API?

Yes. Because Airbyte carries its source, destination, and connection details in the request body, you scope your agent by operation in your own self-hosted Jentic One instance, where your rules decide which Airbyte calls and credentials the agent may use. For example, you can allow it to trigger jobs with POST /jobs and poll GET /jobs/{jobId} while leaving out source creation via POST /sources or destination creation via POST /destinations. The agent can only call the operations you expose, and the bearer credentials stay in your instance rather than reaching the agent.

Airbyte API

Connect the Airbyte API to your agent

Capabilities

Start building with Airbyte API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs