Skip to main content
POST
Create Workspace
Any logged-in account can call this — creation itself isn’t gated by a permission, it’s gated by plan. An API key needs the workspaces:write scope.
Four seed roles are created with the workspace: Admin (every permission except snapshots:manage — restoring/deleting a snapshot is too destructive to grant by default — and blob:read/blob:manage, since Blob Storage files are the owner’s data), Developer, Operator and Viewer. They’re ordinary roles from the moment they’re created — renamable, editable, deletable — and count toward the plan’s role cap like any other.

Body

string
required
1–50 characters. Unique per owner among your active (non-deleted) workspaces. The name is stored in lowercase, so Production is saved as production (and conflicts with an existing production).
string
Up to 200 characters.

Response

Same shape as Get Workspace, including the members, the four seed roles, permissions and is_owner.

Errors

Last modified on October 26, 2026