Skip to content

API & CLI

REST API, CLI, OpenStack and S3 compatibility, Terraform, SDK languages.

API surface

Cloud Digit exposes services through several API layers:

Layer What
Cloud Digit REST API Cloud Digit-native API for compute, networking, storage, K8s, etc.
OpenStack-compatible Nova, Neutron, Cinder, Glance, Keystone APIs for VM, volume, image
S3-compatible Object storage; see Object Storage
Kafka, Postgres, MySQL, etc. Standard engine APIs for managed databases

Endpoints

Region Cloud Digit API Console
bd-dha-1 https://api.bd-dha-1.clouddigit.ai/v1 https://my.clouddigit.ai/
bd-ctg-1 https://api.bd-ctg-1.clouddigit.ai/v1
bd-syl-1 https://api.bd-syl-1.clouddigit.ai/v1

Current operational ingresses

The *.clouddigit.ai hostnames above are the forward-looking, customer-facing addresses the platform will use once the white-label DNS cutover completes. Today, the platform is served from *.mymine.space ingresses, for example:

Service Forward-looking (*.clouddigit.ai) Current (*.mymine.space)
Console https://my.clouddigit.ai/ https://cloud.mymine.space/
Support portal https://support.clouddigit.ai/ https://support.mymine.space/
Identity (Keycloak) https://auth.clouddigit.ai/ https://keycloak.mymine.space/
Status https://status.clouddigit.ai/ https://status.mymine.space/
API (per-region) https://api.bd-dha-1.clouddigit.ai/v1 https://api.bd-dha-1.mymine.space/v1
S3 (per-region) https://s3.bd-dha-1.clouddigit.ai https://s3.bd-dha-1.mymine.space
Container registry https://registry.bd-dha-1.clouddigit.ai https://registry.bd-dha-1.mymine.space

Both sets resolve to the same backend infrastructure; the *.clouddigit.ai hostnames become canonical at cutover and the *.mymine.space hostnames continue to work as aliases for at least the first 12 months after cutover. Your welcome email always quotes the URL that is current for your account at sign-up.

Authentication

  • API tokens — long-lived, scoped to project + role
  • OIDC — short-lived bearer tokens via Cloud Digit IAM, suitable for CI/CD
  • OpenStack Keystone tokens — for OpenStack-API consumers
  • AWS-V4 signature — for S3-compatible endpoints
  • MFA-step-up — required for destructive ops on certain resources (e.g., disabling Object Lock)

CLI

Cloud Digit ships a CLI: cd. Install via:

bash curl -sSL https://cli.clouddigit.ai/install.sh | sh

bash brew install clouddigit/tap/cd

powershell winget install ClouddigitBangladesh.CLI

bash git clone https://github.com/clouddigit-bd/cd-cli && cd cd-cli && go install ./...

Configure once:

```bash cd configure

prompts for region, API token, default project

```

Terraform

Provider: clouddigit-bd/clouddigit (registry coordinates pending publish; until then, install via terraform.required_providers with the GitHub source).

```hcl terraform { required_providers { clouddigit = { source = "clouddigit-bd/clouddigit" version = ">= 0.5.0" } } }

provider "clouddigit" { region = "bd-dha-1" # token via env var CD_API_TOKEN }

resource "clouddigit_vm" "web" { name = "web-01" flavor = "std-2x8" image = "ubuntu-24.04" vpc_id = clouddigit_vpc.default.id subnet_id = clouddigit_subnet.public.id ssh_key = clouddigit_ssh_key.admin.id } ```

SDKs

Official SDKs (track current versions in the relevant repo):

  • Python — pip install clouddigit
  • Go — go get github.com/clouddigit-bd/cd-sdk-go
  • TypeScript / Node — npm install @clouddigit/sdk
  • Java — Maven bd.clouddigit:cd-sdk

For OpenStack APIs, use the standard OpenStack SDKs in any language. For S3 APIs, use any AWS SDK with the Cloud Digit endpoint URL.

Rate limits

API Default
Cloud Digit REST 60 req/s burst, 30 req/s sustained per token
OpenStack Compute (Nova) Per OpenStack defaults
OpenStack Network (Neutron) Per OpenStack defaults
S3 Per-bucket; thousands of req/s sustained

429 responses include a Retry-After header.

Versioning

v1 is the current stable Cloud Digit REST major version. Breaking changes are introduced as v2 only after a deprecation window of at least 12 months on v1.