Hubfly spaceDocs
Console

API · Managed Databases

Managed Databases API

Create and operate PostgreSQL, MySQL and SQLite/libSQL instances through the Hubfly space Dashboard API.

Which API to use

Instance management uses https://api.hubfly.space/api/v1 with a Dashboard bearer token. Instance routes live under /projects/:projectId/managed/instances/:instanceId, where :projectId is a project of type managed. The catalog and price estimate are account-level reads without a project ID.

Your application talks to the database itself over the engine's own protocol with TLS (PostgreSQL and MySQL wire protocols, libSQL over HTTPS). The Dashboard API returns the connection details; it does not proxy application traffic. See Managed Databases for connection guides.

Endpoint groups

These groups cover 69 endpoints. The catalog, pricing, lifecycle, network, operations, logs, metrics, alerts and audit routes are shared with Realtime; the same instance routes serve both products.

Asynchronous operations

Create, start, stop, restart, resize, upgrade, delete and export return an operationId before the work has finished. Poll GET /api/v1/projects/:projectId/managed/instances/:instanceId/operations/:operationId until it reaches a final state, and send one change at a time: a second change while one is running is refused.

Request guards

  • Price quotes. Create and resize send quotedHourlyTotal, the hourly total from GET /api/v1/pricing/managed/estimate. If the price changed, the call returns 409 MANAGED_PRICE_CHANGED; fetch a new quote and retry.
  • Idempotency. Create requires an idempotencyKey (up to 128 characters). Retrying with the same key returns the original instance instead of creating a second one.
  • Typed confirmation. Deleting an instance requires its name in confirmName and fails while deletion protection is on.
  • Revisions. Allowlist updates send the network revision and configuration changes send the config generation you last read, so concurrent edits are not overwritten.

Secrets are shown once

Passwords for new or rotated users and new libSQL tokens are returned only in the response that creates them. The admin password can be revealed again on request, and every reveal is recorded in the audit trail. Never log these responses.

Permissions and errors

Each endpoint lists the permission it needs: database:read, database:query or database:admin. Organization roles grant them; a scoped token must hold the exact permission the route requires. Calling a database route on a realtime server returns 409 MANAGED_FEATURE_UNSUPPORTED, and an unknown instance returns 404 MANAGED_INSTANCE_NOT_FOUND. See authentication for tokens and errors for the error envelope.

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top