dbt Cloud API

Name: dbt Cloud API 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.

Quickstart

Get started with dbt Cloud API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a dbt Cloud job run"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with dbt Cloud API 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

Cancel a long-running job that is blocking a deployment or analytics window

GET STARTED

Start building with dbt Cloud API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for dbt Cloud API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for dbt Cloud API, keeping it validated and agent-ready. dbt Cloud is the hosted environment for dbt, the analytics engineering tool used by data teams to model and transform warehouse data. The v3 API exposes accounts, projects, jobs, runs, environments, and connections across 12 endpoints, including the ability to trigger and cancel runs programmatically. It is most often used to integrate dbt jobs into orchestration tools, alerting pipelines, and data CI/CD setups.

Use Cases

Patterns agents use dbt Cloud API 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 though 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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Airbyte

Open-source data integration platform that loads sources to a warehouse before dbt transforms them.

Use Airbyte alongside dbt Cloud to handle the EL portion of EL-T, then trigger dbt jobs from Airbyte sync completion events.

Complementary

Snowflake

Cloud data warehouse that dbt Cloud commonly transforms data inside.

Use Snowflake alongside dbt Cloud when you need to query transformed tables or check warehouse usage between dbt runs.

Complementary

Prefect

Workflow orchestration platform that can call dbt Cloud as a step in a wider DAG.

Use Prefect alongside dbt Cloud when transformations must run as part of a larger orchestrated pipeline with retries, branches, and SLAs.

FAQs

Specific to using dbt Cloud API 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.