Database Migration API Python API Docs | dltHub

Google's Database Migration API offers RESTful endpoints to manage migration jobs and connection profiles programmatically. The API is part of the Database Migration Service, enabling efficient database transfers to Google Cloud. Use it to automate migration tasks. The REST API base URL is https://datamigration.googleapis.com and All requests require Google Cloud OAuth2 (Bearer) credentials..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Database Migration API data in under 10 minutes.

---

What data can I load from Database Migration API?

Here are some of the endpoints you can load from Database Migration API:

---

How do I authenticate with the Database Migration API API?

The API uses Google Cloud OAuth2. Requests must include an Authorization: Bearer <ACCESS_TOKEN> header. Credentials are obtained via user access tokens or service‑account tokens.

1. Get your credentials

1. Enable the Database Migration API in Google Cloud Console for your project.
2. Create or use a service account with the appropriate IAM role (e.g., Database Migration Admin).
3. Grant the service account the required roles.
4. Create and download a JSON key for the service account (or use Workload Identity).
5. Obtain an access token: a) gcloud auth application-default login (user) or b) gcloud auth activate-service-account --key-file=KEY.json then gcloud auth print-access-token; or c) exchange the service‑account JWT for an OAuth2 token via the Google OAuth2 token endpoint.
6. Include the token in requests with the header Authorization: Bearer <ACCESS_TOKEN>.

2. Add them to .dlt/secrets.toml

Copy
[sources.database_migration_api_source]
token = "your_oauth2_access_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Database Migration API API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python database_migration_api_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline database_migration_api_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset database_migration_api_data
The duckdb destination used duckdb:/database_migration_api.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline database_migration_api_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads connection_profiles and migration_jobs from the Database Migration API API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def database_migration_api_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://datamigration.googleapis.com",
            "auth": {
                "type": "bearer",
                "token": token,
            },
        },
        "resources": [
            {"name": "connection_profiles", "endpoint": {"path": "v1/{parent}/connectionProfiles", "data_selector": "connectionProfiles"}},
            {"name": "migration_jobs", "endpoint": {"path": "v1/{parent}/migrationJobs", "data_selector": "migrationJobs"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="database_migration_api_pipeline",
        destination="duckdb",
        dataset_name="database_migration_api_data",
    )
    load_info = pipeline.run(database_migration_api_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("database_migration_api_pipeline").dataset()
sessions_df = data.projects_locations_connection_profiles.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM database_migration_api_data.projects_locations_connection_profiles LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("database_migration_api_pipeline").dataset()
data.projects_locations_connection_profiles.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load Database Migration API data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack