The REST API is the layer the console, the kc CLI and the Terraform provider all sit on top of. Every resource is created or updated with a single PUT of a kubectl-style envelope (apiVersion / kind / metadata / spec) — exactly what kc get -o json prints. The interactive HTTP reference lives at cloud-api.kvindo.com/swagger.

The easiest way to drive it from code is the official Python SDK (kc-sdk-python), a thin wrapper over the same HTTP endpoints. These pages use it; the raw HTTP call each method maps to is noted on the per-endpoint pages under Design ideas.

Install & authenticate

Install from PyPI and construct a KcClient with a bearer token (create one in the console under IAM → Tokens → Create token; shown once) and the base URL — https://cloud-api.kvindo.com, or the https://cloud-api.kvindo.ru mirror:

A first resource

Calls that change state (create_or_update, delete) are asynchronous: they return a requestId immediately, then the resource reconciles in the background. Poll it with wait_request_satisfied(requestId, timeout), then read the resource back with read(id) (which exposes it under .resource):

Related pages

More in this section

• Design ideas
• Examples

Reference

• Interactive API reference (Swagger)
• kc-sdk-python on PyPI