Google Cloud Data Fusion API
Browse all Google APIs✓ Official Vendor SpecAnalyticsData Pipelinesoauth215 EndpointsREST
For Agents
Provision and lifecycle Cloud Data Fusion instances, manage DNS peerings, and list available versions. Lets agents stand up the data integration platform without going through the Cloud Console.
Use for: I need to provision a new Cloud Data Fusion instance in europe-west1, Restart an existing Data Fusion instance after a config change, List available Data Fusion versions for the Enterprise edition, Set up a DNS peering so my Data Fusion instance can reach an on-prem name server
Not supported: Does not design pipelines, run pipeline executions, or expose CDAP plugins — use for Data Fusion instance provisioning, lifecycle, and DNS peering only.
Cloud Data Fusion is a fully-managed, cloud-native data integration service for building and operating ETL/ELT pipelines through a graphical pipeline designer. The API exposes 15 endpoints that provision and lifecycle Data Fusion instances, manage DNS peerings, and inspect available platform versions. It is the control-plane API: pipeline design and execution happen inside the instance UI and the per-instance CDAP REST API.
Install Jentic One Beta
Connect the Cloud Data Fusion API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Data Fusion 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.
1
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 | sh2
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 instanceJentic 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 Cloud Data Fusion API.
Provision Cloud Data Fusion instances in a chosen region and edition
Restart, upgrade, and delete Data Fusion instances through the API
Configure DNS peerings so instances can resolve private network services
List available Data Fusion versions before creating an instance
Track long-running operations for instance create and upgrade calls
Inspect instance state, edition, and connectivity before pipelines are deployed
Use Cases
Patterns agents use Cloud Data Fusion API for, with concrete tasks.
★ Programmatic Data Fusion Instance Provisioning
Stand up Cloud Data Fusion instances from infrastructure-as-code or an agent workflow rather than the Cloud Console. The API accepts edition, version, and network settings on create and exposes long-running operations to wait for the instance to reach the RUNNING state. End-to-end provisioning typically completes in 15-25 minutes once the create call returns.
Create a Cloud Data Fusion instance named 'analytics-prod' in us-central1 with edition ENTERPRISE and the latest available version, then poll the operation until state is RUNNING
Private Network DNS Peering Setup
Configure DNS peerings on a Data Fusion instance so pipelines running inside the tenant project can resolve private hostnames in the customer VPC. Without the peering, pipelines fail to reach on-prem databases, internal Cloud SQL endpoints, or private DNS zones. The API handles create, list, get, update, and delete on the dnsPeerings collection.
Create a DNS peering on instance 'analytics-prod' for domain 'corp.internal.' targeting the customer VPC's private DNS zone
Instance Lifecycle Automation in CI/CD
Spin up ephemeral Data Fusion instances for staging tests, run pipeline validation jobs, and tear them down to control cost. The API's restart, upgrade, and delete operations let CI pipelines drive the full lifecycle from a build job. Combined with version listing, this supports automated upgrade-test-promote flows.
Upgrade Data Fusion instance 'staging' to version 6.10.0 and wait for the operation to complete, then restart the instance and confirm state is RUNNING
AI Agent Provisioning Operator
An AI agent can provision and lifecycle Data Fusion instances through Jentic without the operator writing OAuth code. Jentic's intent search returns the matching create, restart, upgrade, or delete operation, the agent loads the schema, and Jentic executes against the Data Fusion control plane with vault-stored credentials. This compresses platform-engineering setup work that normally takes a developer multiple days.
Use Jentic to search 'create a data fusion instance', load the create-instance schema, and execute it for project 'acme-data', region 'us-central1', edition 'BASIC'
Key Endpoints
15 endpoints — cloud data fusion is a fully-managed, cloud-native data integration service for building and operating etl/elt pipelines through a graphical pipeline designer.
METHOD
PATH
DESCRIPTION
POST
/v1/{+parent}/instances
Create a Data Fusion instance
GET
/v1/{+parent}/instances
List Data Fusion instances in a location
POST
/v1/{+name}:restart
Restart a Data Fusion instance
POST
/v1/{+parent}/dnsPeerings
Create a DNS peering on an instance
GET
/v1/{+parent}/versions
List available Data Fusion versions
POST
/v1/{+name}:cancel
Cancel a long-running operation
POST
/v1/{+parent}/instances
Create a Data Fusion instance
GET
/v1/{+parent}/instances
List Data Fusion instances in a location
POST
/v1/{+name}:restart
Restart a Data Fusion instance
POST
/v1/{+parent}/dnsPeerings
Create a DNS peering on an instance
GET
/v1/{+parent}/versions
List available Data Fusion versions
POST
/v1/{+name}:cancel
Cancel a long-running operation
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google OAuth client secrets and refresh tokens are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access tokens for datafusion.googleapis.com; raw client credentials never enter the agent context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'provision a data fusion instance') and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without browsing the discovery doc.
Time to first call
Direct Data Fusion integration: 1-3 days for OAuth, long-running-operation polling, and edition/version handling. Through Jentic: under 1 hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Data Fusion API through Jentic.
What authentication does the Cloud Data Fusion API use?
The Cloud Data Fusion API uses OAuth 2.0 with the cloud-platform scope. Through Jentic the OAuth client and refresh tokens live in the Jentic vault and the agent receives short-lived scoped access tokens, so raw Google credentials never enter the agent context.
Can I run pipelines through the Cloud Data Fusion API?
No — the Data Fusion control-plane API at datafusion.googleapis.com only provisions and lifecycles instances. Pipeline create, deploy, and run operations are exposed by the per-instance CDAP REST API, served from the running instance's URL once it is provisioned through this API.
What are the rate limits for the Cloud Data Fusion API?
Google enforces standard Cloud quotas on Data Fusion: per-project quotas on number of instances per edition, plus general read/write rate limits on the operations and dnsPeerings collections. Quotas are visible in the Cloud Console under IAM and admin, quotas, filtered to datafusion.googleapis.com.
How do I provision a Data Fusion instance through Jentic?
Search Jentic for 'create a data fusion instance', load the schema for POST /v1/{+parent}/instances, and execute with project, location, edition, and version. Jentic returns the long-running operation name; poll GET /v1/{+name} on it until done is true.
Is the Cloud Data Fusion API free?
API calls themselves are free, but Data Fusion instances are billed by edition (Developer, Basic, Enterprise) and runtime hours, plus underlying Dataproc and BigQuery costs incurred by pipelines. There is no per-API-call charge.
Which versions can I create an instance with?
Call GET /v1/{+parent}/versions on the location to list available Data Fusion versions before creating an instance. The response includes version IDs and default flag, so an agent can pick the latest stable version programmatically rather than hard-coding it.
GET STARTED