VK Cloud Python API Docs | dltHub

Build a VK Cloud-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

VK Cloud's REST API endpoints facilitate interaction with VK Cloud services, requiring authentication tokens in some cases. The main documentation covers connection specifics and endpoint details. For S3 storage, refer to the REST API documentation. The REST API base URL is Region- and service-specific. See API Endpoints for your region in VK Cloud management console. Example service base URLs (Moscow region): https://infra.mail.ru:8774/v2.1 (nova), https://public.infra.mail.ru:8776/v3/<project_id> (cinder), https://infra.mail.ru:9292 (glance), https://mcs.mail.ru/infra/karboii/v1 (karboii), https://public.infra.mail.ru:8786/v2/<project_id> (manila). (Note: replace <project_id> with your project ID.) and Requests require an OpenStack Keystone token (X-Subject-Token/X-Auth-Token) for authentication..

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 VK Cloud data in under 10 minutes.


What data can I load from VK Cloud?

Here are some of the endpoints you can load from VK Cloud:

ResourceEndpointMethodData selectorDescription
servershttps://infra.mail.ru:8774/v2.1/serversGETserversList cloud servers (nova list)
imageshttps://infra.mail.ru:9292/v2/imagesGETimagesList VM images (glance)
volumeshttps://public.infra.mail.ru:8776/v3/<project_id>/volumesGETvolumesList block storage volumes (cinder)
snapshotshttps://public.infra.mail.ru:8776/v3/<project_id>/snapshotsGETsnapshotsList volume snapshots (cinder)
shareshttps://public.infra.mail.ru:8786/v2/<project_id>/sharesGETsharesList file shares (manila)
backupshttps://mcs.mail.ru/infra/karboii/v1/backupsGETbackupsList VM/database backups (karboii)
logshttps://mcs.mail.ru/cloudlogs/v1/logsGETlogsRetrieve VM logs (cloudlogs)

How do I authenticate with the VK Cloud API?

Obtain a Keystone access token (X-Subject-Token) via the VK Cloud API; include it in requests using the X-Auth-Token or X-Subject-Token header. Some endpoints also require project_id in the path.

1. Get your credentials

  1. Enable API access for your project in VK Cloud management console under Project settings → API Access. 2) Use the VK Cloud API identity/Keystone authentication flow (see "Getting a Keystone access token") to authenticate and receive an X-Subject-Token. 3) Save that token for use in request headers (X-Auth-Token / X-Subject-Token). 4) Obtain your Project ID from Project settings (API access / Terraform tab) for endpoints that require <project_id>.

2. Add them to .dlt/secrets.toml

[sources.vk_cloud_source] keystone_token = "your_keystone_token_here" project_id = "your_project_id_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:

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

1. Install the dlt AI Workbench:

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:

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 VK Cloud 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:

python vk_cloud_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline vk_cloud_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 servers and images from the VK Cloud API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def vk_cloud_source(keystone_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "Region- and service-specific. See API Endpoints for your region in VK Cloud management console. Example service base URLs (Moscow region): https://infra.mail.ru:8774/v2.1 (nova), https://public.infra.mail.ru:8776/v3/<project_id> (cinder), https://infra.mail.ru:9292 (glance), https://mcs.mail.ru/infra/karboii/v1 (karboii), https://public.infra.mail.ru:8786/v2/<project_id> (manila). (Note: replace <project_id> with your project ID.)", "auth": { "type": "bearer", "token": keystone_token, }, }, "resources": [ {"name": "servers", "endpoint": {"path": "https://infra.mail.ru:8774/v2.1/servers", "data_selector": "servers"}}, {"name": "images", "endpoint": {"path": "https://infra.mail.ru:9292/v2/images", "data_selector": "images"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="vk_cloud_pipeline", destination="duckdb", dataset_name="vk_cloud_data", ) load_info = pipeline.run(vk_cloud_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):

import dlt data = dlt.pipeline("vk_cloud_pipeline").dataset() sessions_df = data.servers.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM vk_cloud_data.servers LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("vk_cloud_pipeline").dataset() data.servers.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 VK Cloud data to?

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

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for VK Cloud?

Request dlt skills, commands, AGENT.md files, and AI-native context.