Quick Start
How It Works
| Operation | Endpoint | Description |
|---|---|---|
| Create | POST /api/v1/workspaces/ | Create new workspace |
| List | GET /api/v1/workspaces/ | List user workspaces |
| Get | GET /api/v1/workspaces/{id} | Get specific workspace |
| Update | PATCH /api/v1/workspaces/{id} | Update workspace |
| Delete | DELETE /api/v1/workspaces/{id} | Delete workspace |
API Reference
Create Workspace
Creates a new workspace with the specified configuration.List Workspaces
Retrieves paginated list of user’s workspaces.limit(int): Results per page (default: 10, max: 100)offset(int): Pagination offset (default: 0)
Update Workspace
Updates workspace properties using partial data.Python SDK Examples
Basic Operations
Advanced Management
Key Concepts
Workspace Slug
Workspace Slug
URL-friendly identifier that’s auto-generated from name if not provided. Must be unique across the platform. Used for friendly URLs like
/workspace/my-team.Multi-tenancy
Multi-tenancy
Users can own or belong to multiple workspaces. Access control ensures users only see workspaces they have permissions for.
Settings Object
Settings Object
Flexible JSON dictionary for workspace-level configuration like themes, notification preferences, or feature toggles.
Organizational Hierarchy
Organizational Hierarchy
Workspaces → Projects → Issues/Agents/Tasks. Workspaces provide the top-level boundary for organizing work and team access.
Best Practices
Naming Convention
Naming Convention
Use descriptive names that reflect the team or purpose. Avoid generic names like “Workspace 1”. Good examples: “Marketing Team”, “Backend Services”, “Client Projects”.
Slug Management
Slug Management
Choose memorable slugs for URLs. Use hyphens, not underscores. Keep them short but descriptive:
marketing-team not marketing_team_workspace_2024.Settings Strategy
Settings Strategy
Use settings for workspace-wide preferences. Store user preferences separately. Common settings:
theme, defaultProject, notifications.Access Control
Access Control
Plan member permissions before inviting users. Consider using role-based access with workspace-level roles like
owner, admin, member.Testing
Test workspace operations to ensure proper functionality:Related
Projects
Organize work within workspaces using projects
Members
Manage team access and permissions

