Chelabase
ManagementBranches

List a branch's Postgres databases

GET
/v1/databases/{id}/branches/{branch_id}/databases

The databases of the branch's Postgres cluster: the main one first, then by name. The cluster's own postgres database is listed with origin system. Pass a name as database to the connection details. Each carries its data API state and default schema.

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Database id

Formatuuid
branch_id*string

Branch id

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/databases/497f6eca-6276-4993-bfeb-53cbbbba6f08/branches/497f6eca-6276-4993-bfeb-53cbbbba6f08/databases"
[  {    "data_api": "off",    "data_api_error": "string",    "default_schema": "string",    "main": true,    "name": "string",    "origin": "main",    "owner": "string"  }]

Reveal a branch's connection details GET

The connection details of the branch's owner, or of the role named by `role`, for its main database or the one named by `database`. `password` is null, with the reason in `password_state`, when it can't be shown: a role whose password was set in SQL (only its hash is stored) or has an MD5 hash the proxy can't use; the `uri` then has no password. Never cached (`Cache-Control: no-store`) and never logged.

List a branch's guard exemptions GET

The login roles, by name, that the branch's "guard login roles" switch leaves alone: on a protected branch with `guard_logins` on, they may still change the schema. Sorted by name (byte order). A new branch copies its parent's.