CraneBase

CraneBase endpoints work on the account’s CraneBase (managed database) services, with a full access key or a key scoped to the service. Reads (every GET, the backup download link included) need the scope’s read permission; everything that changes something needs write. A service that isn’t on the account, or isn’t a CraneBase service, is 404; a key without the permission gets 403. The plan sets how many databases and snapshots a service may hold, and going over is refused with 400. When the database server refuses a change or can’t be reached, the call fails with 400 and the server’s message (500 with a general one for snapshots and deletes).

Names: CraneBase puts sql{serviceId}_ in front of every database and user you create, so shop on service 1042 becomes sql1042_shop. Everywhere else (paths, grant, revoke, snapshots, restores) takes the full name, as the list endpoints return it.

Hosts: a database user can only connect from the service’s hosts (an IPv4 address, or % for any address). A new user is set up on every host, and a new host gets every existing user. A user with webadmin can also sign in to phpMyAdmin.