Skip to main content
GET
Get the caller's roles

Authorizations

Authorization
string
header
required

Your Reason API key from Settings > API. New keys use reason_; legacy ara_ keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, knowledge:read, memory:read, memory:write, skills:read, skills:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, automations:read, automations:write, agent_auth:read. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:read reads sessions, including the assistant, reasoning and tool activity in their events. sessions:debug is privileged: only for organization owners/admins, it expands session events to the full diagnostic projection (diagnostic event kinds, status text and raw event metadata).

Path Parameters

orgId
string
required

Organization id or slug. Resolve it with GET /v3/self.

Response

The caller's organization role and account product tier.

user_id
string
membership_role
enum<string>

The caller's role in this organization. This is the role that decides what the caller may do in it, and it matches membership_role on the organization.

Available options:
owner,
admin,
member,
viewer
app_role
enum<string>

The caller's app-wide product tier, the same in every organization. It is not a permission level and says nothing about the caller's role in this organization; see membership_role.

Available options:
pro,
regular