Managed Databases API

API endpoints for creating and managing PostgreSQL, Redis, and ClickHouse instances.

PostgreSQL

List databases

GET /v1/databases

Returns all PostgreSQL instances for the authenticated user.

Example

curl https://api.redu.cloud/v1/databases \
  -H "x-api-key: YOUR_API_KEY"

Create database

POST /v1/databases

Request body

Response, the password is returned once and not stored in plain text.

{
  "id": 1,
  "name": "my-db",
  "db_name": "app",
  "db_user": "appuser",
  "db_password": "the-plaintext-password-shown-once",
  "db_version": "16",
  "status": "provisioning",
  "floating_ip": null,
  "port": 5432,
  "created_at": "2026-05-30T12:00:00Z"
}

Get database

GET /v1/databases/:id

Delete database

DELETE /v1/databases/:id

Returns 204 No Content.

Redis

List Redis instances

GET /v1/redis

Create Redis instance

POST /v1/redis

Request body

Response

{
  "id": 1,
  "name": "my-cache",
  "version": "7",
  "password": "the-plaintext-password-shown-once",
  "status": "provisioning",
  "floating_ip": null,
  "port": 6379,
  "created_at": "2026-05-30T12:00:00Z"
}

Get Redis instance

GET /v1/redis/:id

Delete Redis instance

DELETE /v1/redis/:id

Returns 204 No Content.

ClickHouse

ClickHouse is a column-oriented database for analytics (OLAP). It is a distinct managed resource, HTTP on port 8123.

List ClickHouse instances

GET /v1/clickhouse

Create ClickHouse instance

POST /v1/clickhouse

Request body

Response, the password is returned once.

{
  "id": 1,
  "name": "my-analytics",
  "db_name": "analytics",
  "db_user": "appuser",
  "db_password": "the-plaintext-password-shown-once",
  "status": "provisioning",
  "floating_ip": null,
  "port": 8123,
  "created_at": "2026-05-30T12:00:00Z"
}

Get ClickHouse instance

GET /v1/clickhouse/:id

Delete ClickHouse instance

DELETE /v1/clickhouse/:id

Returns 204 No Content.

High availability

POST /v1/databases and POST /v1/clickhouse accept "ha": true, which provisions three machines with automatic failover instead of one, behind a single load balancer address. Connect to that address rather than to any individual member: it is what stays valid when a machine dies.

/v1/redis and /v1/relational-databases (MySQL, MariaDB) do not accept the field. Sending it there fails validation rather than returning a single machine you might believe is redundant.

It roughly triples the cost of the resource, so it is never a default and never inferred from the flavor. If you are calling this on a user’s behalf, show them the cost before you send the request.

Behaviour during a real machine loss, with the measured numbers and the limits: Database high availability.

Status values