REST API: organization

Use these endpoints to read your organization's roster. GET /organization/members lists current members, including their organization role. GET /organization/invitations lists invitations that have been sent but not yet accepted. Neither endpoint sends an invitation, changes a role, or removes a member — the API surface today is read-only. Manage membership itself from the dashboard.

Build your own provisioning or compliance reporting against these endpoints instead of scraping the dashboard. For example, reconcile organization membership against your identity provider on a schedule, or flag an invitation that has stayed pending too long.

For custom-role assignment on a member, see REST API: roles and members. That is a separate capability from the plain roster these two endpoints return: a member's organization role (owner, admin, member) is distinct from any custom role your organization has defined.

These endpoints require organization-administration access. An MCP client reaches the same data through dedicated list_members and list_invitations tools, gated on the mcp:admin scope described in MCP scopes.