Retrieve a vector store permission
Returns the role a principal effectively holds on the vector store and where it comes from: owner, a permission granted to it (grant), the store’s team permission, or none. A principal with none can still reach the store as an organization admin of its team; that is decided per request from the caller’s role. Anyone who can read the store can call this. Returns 410 once the vector store has expired.
Authorizations
Gateway auth: send Authorization: Bearer <mka1-api-key>. For multi-user server-side integrations, you can also send X-On-Behalf-Of: <external-user-id>.
Headers
Optional external end-user identifier forwarded by the API gateway.
Path Parameters
The ID of the vector store.
The principal: a member's user id, the end-user id a request is delegated to with X-On-Behalf-Of, or 'team' for the permission that applies to every member of the store's team.
1Response
OK
The effective permission of one principal on a vector store, with where it comes from.
The object type, which is always 'vector_store.permission'.
The ID of the vector store the permission applies to.
Who the permission applies to: one principal (user), or every member of the store's team (team).
user, team The principal the permission applies to: a member's user id, or the end-user id a request is delegated to with X-On-Behalf-Of. null when the permission applies to the store's team.
The highest role the principal holds on the store, or null when it holds none.
owner, writer, reader Where the role comes from: the store's owner, a permission held by this principal, the store's team permission, or nothing — the principal reaches the store only as an org admin of its team, if at all.
owner, grant, team, none