Skip to main content
Clumio provides a REST API, Python and Go SDKs, and a Terraform provider. Its MCP repository generates Terraform configuration for a smaller set of workflows.

​
Pick your entry point

​
Get a token first

The REST API, SDKs, and Terraform provider use a long-lived bearer token. Generate one from Administration → Access management → API tokens. See Authentication for token types, base URLs, and rotation.
The Terraform provider reads CLUMIO_API_TOKEN and CLUMIO_API_BASE_URL. The SDKs accept the same token and a hostname through their configuration objects.

​
What the API covers

Protection

Policy definitions, protection groups, protection rules, and the tag-based bindings that enrol resources automatically.

Restore

Granular restores of objects, tables, files and databases, to the source or any authorised account and region.

Discovery

A machine-readable Discovery API that maps resources to their operation IDs, so clients can walk the surface without hardcoding endpoint lists.

Audit and inventory

Assets, tasks, alerts, users, organisational units and compliance reporting.

​
API conventions

  • Per-resource versioning. Resources are versioned independently and selected through the Accept header, so a change to one resource does not force a client-wide upgrade.
  • HAL + HATEOAS responses. Responses carry links to related resources and valid actions, which is how the Discovery API stays accurate without a separate registry.
  • Regional base URLs. Calls go to the API base URL matching the control plane where the token was created. See Authentication for the values published by the Terraform provider.

​
Where these live

Open an issue or contact Clumio about a public tool missing from this index.