Skip to main content
POST
Create an organization

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:debug is privileged: it expands diagnostic session events only for organization owners/admins.

Body

application/json
name
string
required
slug
string

Optional URL slug; generated from the name when omitted.

Response

Created.

id
string
org_id
string
name
string
slug
string
membership_role
enum<string>

The caller's membership role in this organization. This is not an app-wide product role.

Available options:
owner,
admin,
member,
viewer
plan
string | null
created_at
string<date-time>