Getdbt dbt Cloud API

Name: dbt Cloud API
Brand: dbt Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsData Pipelinesbearer12 EndpointsREST

For Agents

Trigger and monitor dbt Cloud transformation jobs, list projects and environments, cancel running jobs, and inspect run metadata for analytics engineering pipelines. Authenticated with personal access tokens or service account tokens.

Install Jentic One Beta

Connect the dbt Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the dbt Cloud 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 dbt Cloud API.

Trigger a dbt Cloud job run on demand from an upstream data-loading event

Monitor a run's status until success or failure to gate downstream pipeline steps

List jobs within an account to inventory transformation workloads for documentation

GET STARTED

Start building with dbt Cloud API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use dbt Cloud API for, with concrete tasks.

★ EL-Triggered Transformation

Modern data stacks load raw data via tools like Fivetran or Airbyte and then transform it with dbt. The dbt Cloud API's trigger endpoint lets the loader call dbt the moment data lands, replacing time-based scheduling with event-driven runs and tightening freshness for downstream dashboards.

On a Fivetran webhook for sync completion, call `POST /accounts/{account_id}/jobs/{job_id}/run` and store the returned run ID for monitoring.

Run Monitoring and Alerting

Data teams want alerts when a dbt run fails or runs unusually long. The API exposes a run-detail endpoint that returns status, duration, and step-level metadata, so a polling job or orchestrator can monitor active runs and emit alerts based on real state rather than scheduled assumptions.

Poll `GET /accounts/{account_id}/runs/{run_id}` every 30 seconds until status is success or failure and emit an alert if duration exceeds the SLA.

Orchestrator-Driven dbt Step

Workflow tools like Airflow, Dagster, or Prefect often need to call dbt as a step in a wider DAG so transformations sit alongside ingestion and reverse ETL. The API supports trigger and run-status calls suitable for an operator to wrap dbt as a first-class workflow step with retry and SLA handling.

From the orchestrator task, call `POST /accounts/{account_id}/jobs/{job_id}/run`, then poll `GET /accounts/{account_id}/runs/{run_id}` and surface the final status to the workflow.

Agent-Driven Data Operations

An AI agent in a data-ops chat tool can resolve 'rerun the customers job' by discovering the trigger operation through Jentic and executing it. The agent hands off the bearer token management to Jentic and reports back the run ID and status link, so analysts get a single conversational entry point for dbt operations.

Resolve the job ID for the 'customers' job, call `POST /accounts/{account_id}/jobs/{job_id}/run` via Jentic, and reply with the run ID and link.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for dbt cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/accounts/{account_id}/jobs/{job_id}/run

Trigger a job run

GET

/accounts/{account_id}/runs/{run_id}

Get run details

POST

/accounts/{account_id}/runs/{run_id}/cancel

Cancel a run

GET

/accounts/{account_id}/jobs

List jobs

GET

/accounts/{account_id}/projects

List projects

GET

/accounts/{account_id}/environments

List environments

GET

/accounts/{account_id}/connections

List connections

POST

/accounts/{account_id}/jobs/{job_id}/run

Trigger a job run

GET

/accounts/{account_id}/runs/{run_id}

Get run details

POST

/accounts/{account_id}/runs/{run_id}/cancel

Cancel a run

GET

/accounts/{account_id}/jobs

List jobs

GET

/accounts/{account_id}/projects

List projects

Why Jentic?

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

Credential isolation

dbt Cloud bearer tokens (personal access or service account) are stored encrypted in the Jentic vault. Agents call dbt Cloud operations via Jentic and the platform injects the `Authorization: Bearer …` header at runtime — the raw token never enters the agent's prompt.

Intent-based discovery

Agents search Jentic by intent (e.g. 'trigger a dbt Cloud job' or 'get the status of a dbt run') and Jentic returns the matching dbt Cloud operation with its input schema and account/job/run path parameters.

Time to first call

Direct dbt Cloud integration: a day to handle auth, account scoping, and run-state polling. Through Jentic: under 30 minutes for the first call, reusable across orchestrators and agents.

FAQs

Specific to using dbt Cloud API through Jentic.

Why is there no official OpenAPI spec for dbt Cloud API?

dbt Labs does not publish an OpenAPI specification covering this API surface. Jentic generates and maintains this spec so that AI agents and developers can call dbt Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the dbt Cloud API use?

The dbt Cloud v3 API uses HTTP Bearer authentication with a personal access token or a service account token. Through Jentic, the token is stored encrypted in the vault and injected as `Authorization: Bearer …` at execution time.

Can I trigger a dbt Cloud job programmatically?

Yes. Call `POST /accounts/{account_id}/jobs/{job_id}/run` with the account and job ID. The response includes the run ID, which you then monitor via the runs endpoint.

Can I cancel a running dbt job through the API?

Yes. Call `POST /accounts/{account_id}/runs/{run_id}/cancel` with the account and run ID to stop a job that is in progress.

How do I monitor a dbt run through Jentic?

Search Jentic for `get a dbt Cloud run status`, load the schema for `GET /accounts/{account_id}/runs/{run_id}`, and execute with the run ID. Jentic injects the bearer token automatically.

Does the dbt Cloud API expose model-level results or test failures?

The v3 endpoints in this spec expose run metadata at the run level. For model-level artifacts and tests, you typically combine the run-trigger and status endpoints with dbt's run results artifact downloads or the dedicated metadata API.

Getdbt dbt Cloud API

Connect the dbt Cloud API to your agent

Capabilities

Start building with dbt Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs