---
title: "Create Workspace"
method: POST
path: "/api/workspaces"
tags: ["workspace"]
---

# Create Workspace

`POST /api/workspaces`

## Request

- Base URL: `https://api.heymetra.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.heymetra.com/api/workspaces`
- Auth: none declared

Open another workspace and move into it.

ANYBODY MAY, and that reverses the ruling of 2026-09-14 ("sadece adminler
workspace ekleyebilmeli ve silebilmeli") on the owner's instruction of
2026-09-20. The reasoning: a role says what somebody may do INSIDE a
workspace, and opening a new one is not something that workspace has any
stake in. Being invited to a customer's team as a member should not stop a
person using the product for their own work — which is what the old gate
did, silently, by hiding the control rather than refusing it.

They become the OWNER of what they create, whatever role they hold where
they are standing. Closing a workspace is a different question and keeps
its own gate.

Switching into it is part of creating it: a new workspace you are not
looking at is indistinguishable from nothing having happened.

## Headers

- `authorization` string, nullable
- `x-workspace-id` string, nullable

## Request body

- NewWorkspaceIn
  - `name` string, required

## Response `201`

Successful Response

- NewWorkspaceOut
  - `tenant_id` string, uuid, required
  - `name` string, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/heymetra/apis/heymetra-api.md) · [All operations](https://skmtc.dev/heymetra/apis/heymetra-api/llms.txt) · [OpenAPI document](https://skmtc.dev/heymetra/apis/heymetra-api/revisions/488ce9683884?raw)