list organizations
Uses the selected organization and the authenticated user’s current permissions. Applies the same setup and archive rules as the dashboard.
/api/v1/organizationsAuthorization
ManagementOAuth managementUser-based Clerk OAuth. CLI is a public Authorization Code client using S256 PKCE and browser loopback redirect. Hosted MCP uses resource-bound OAuth. Verify issuer, token type, intended audience/resource, scopes, live membership and current role. Do not forward arbitrary OAuth tokens into Convex session JWT auth. OAuth URLs below are placeholders for deployment configuration.
In: header
Scope: management
Query Parameters
1 <= value <= 10025Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/organizations"{ "items": [ { "id": "string", "name": "string", "role": "string", "plan": "free", "paused": true } ], "nextCursor": "string"}set default organization PUT
Remember the user's account default as an initial organization suggestion; null clears it. This preference does not change an established local CLI organization context or an MCP action's explicit organization target. Every organization-scoped MCP tool invocation supplies organizationId. An inaccessible default causes an explicit choose-organization error; never silently switch to another organization.
create organization POST
User-based OAuth allows organization creation without an existing selected organization. The authenticated user becomes its admin; existing onboarding rules apply.