GET /schema/permission_groups
get_schema_permission_groups
Lists the permission groups the caller may inspect: the script, an Artist and a Vendor see only their own, an Admin person every HumanUser group. In /spec.json since 2026-11-10, in no reference page.
Partly measured. a Manager person; on the probed site none has impersonation on. Blocked on the site
API
Params
| part | value |
|---|---|
permission_rule_set_entity_type |
optional, HumanUser or ApiUser. Defaults to the caller's own kind |
Sample requests
r = c.get("/schema/permission_groups")
{
"data": [{"id": "<id>", "code": "api_admin", "display_name": "API Admin", "entity_type": "ApiUser",
"parent_set_id": null, "updated_at": "<timestamp>"}],
"links": {"self": "/api/v1/schema/permission_groups"}
}
r = c.get("/schema/permission_groups", params={"permission_rule_set_entity_type": "HumanUser"})
{"data": [], "links": {"self": "/api/v1/schema/permission_groups?permission_rule_set_entity_type=HumanUser"}}
Response codes
| status | when |
|---|---|
| 200 | always seen, with an empty data for a kind the caller may not inspect |
As a person, through sudo_as_login (probe 132), ?permission_rule_set_entity_type=HumanUser:
| caller | groups listed |
|---|---|
script, api_admin |
none |
| Admin person | every HumanUser group; five on the probed site |
| Artist | artist only |
| Vendor | vendor only, with or without the parameter (probe 162) |
Edge cases
/spec.jsonsays a caller withoutset_permissionssees only its own group. The script, an API Admin, got its own group and an empty list forHumanUser.codeis what the two child calls take in their path.