List a branch's roles
The branch's owner role first, then the others by name: roles made through the API and roles made in SQL, with their level, password state and the data API secret keys an owner-level role blocks. No passwords: read one with the connection details and role.
Authorization
bearer In: header
Path Parameters
Database id
uuidBranch id
uuidResponse 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/roles"[ { "blocked_keys": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string" } ], "bypass_rls": true, "connection_limit": 0, "created_at": "2019-08-24T14:15:22Z", "guard_exempt": true, "inherit": true, "level": "plain", "login": true, "member_admin": [ "string" ], "member_no_set": [ "string" ], "member_of": [ "string" ], "name": "string", "origin": "owner", "password": "generated", "pending": true, "valid_until": "2019-08-24T14:15:22Z" }]The database's types GET
Every type a column can take in one Postgres database of a branch (base, enum, domain, composite, range and multirange types, with their oids), for a type picker and for joining a table's columns by `type_oid`.
Create a role POST
Creates a role and answers with it. A LOGIN role (the default) gets a generated password; `login: false` makes a NOLOGIN role (a group) with none. `owner_level` gives it the owner's attributes (CREATEROLE, CREATEDB, BYPASSRLS, REPLICATION) and makes it a member of `neon_superuser`. `inherit`, `connection_limit`, `valid_until`, `bypass_rls` and `member_of` set the other allowed attributes and memberships; nothing else can be set. The password isn't in the answer: read it with the connection details and `role`. A role the compute couldn't take yet is `pending` and applied later.