Skip to main content
GET
List Semantic Layer permission recipients
Same contract as the other two axes: active Members only, ids by default, full objects with expand, and picker semantics — a recipient who already holds a grant on the resource you name is omitted, so the list never offers a duplicate.
Owners and Admins are absent by design: they bypass the Semantic Layer permission axis entirely, so a grant to them would change nothing.

Authorizations

x-api-key
string
header
required

API Key authentication. Format: 'x-api-key: api_key'

Response

200 - application/json
groups
string<uuid>[]
required
users
string<uuid>[]
required