Databases

Manage MSSQL, MySQL, and PostgreSQL databases available to an existing hosting plan. Passwords are supplied only when creating or rotating credentials and are never returned by read tools.

Create a database

Call database_get_capacity first. Then call database_create with planId, engine, database name, matching password fields, quota, and an idempotency key. The default application login is created as part of the operation.

Connection settings

database_get_connection_settings returns sanitized host, port, database, username, TLS guidance, and a password-placeholder template. It never returns the current password. Store the password in your application’s secret system.

Users and credentials

• database_list_users lists default and additional logins without passwords.
• database_create_user creates an additional scoped user when the plan supports it.
• database_rotate_credential rotates the default login password.
• database_rotate_user_credential rotates an additional user password.
• database_delete_user cannot delete a protected default user.

Sauvegarde et restauration

database_create_backup queues an engine-appropriate backup into the hosting account's owned /db folder. database_restore_backup accepts only a safe owned /db path and requires the exact databaseId plus explicit overwrite acknowledgement. Use operation_get_status to follow queued work.