---
title: "Create a Team document"
method: POST
path: "/api/team/v1/documents"
tags: ["Team documents"]
---

# Create a Team document

`POST /api/team/v1/documents`

## Request

- Base URL: `https://mdflow.cz`
- URL: `https://mdflow.cz/api/team/v1/documents`
- Auth: HTTP bearer

Creates a markdown document in a Team workspace where the token has write access. Pass `folder_id` to file it into a folder (the folder's workspace wins; a conflicting `workspace_id` is a 400), or `workspace_id` alone to create it at the workspace root. Duplicate sibling titles are automatically disambiguated. Answers 400 once the Team account reaches its 10,000-document cap.

## Request body

- CreateTeamDocumentInput
  - `title` string, required
  - `body` string, required: Markdown document body. UTF-8 encoded content must not exceed 512000 bytes.
  - `folder_id` string, uuid, nullable: Folder to create the document in; its workspace is used. Omit or null for the workspace root.
  - `workspace_id` string, uuid: Team workspace for a root document. Required when folder_id is not set (MDflow never guesses a workspace); must match the folder's workspace when it is.

## Response `201`

Created Team document (without body).

- TeamDocumentListItem
  - `id` string, uuid, required
  - `workspace_id` string, uuid, required: The Team workspace this document belongs to. Never changes.
  - `folder_id` string, uuid, nullable, required: Containing folder, or null for a document at the workspace root.
  - `title` string, required
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required

## Other responses

- `400`: Request body was malformed or failed validation, no workspace could be determined, workspace_id contradicts the folder, or the Team account is at its document cap.
- `401`: Missing, malformed, invalid, or revoked Team access token — including a personal `mdf_` token sent to a Team route, and a token whose creator has left the team. The body includes a `message` with Team token guidance, and the response carries a `WWW-Authenticate` challenge.
- `403`: The Team access token is valid but the operation exceeds its effective access: a write from a read-only token or from a creator whose current workspace permission is read-only, a write while the Team account is not active (setup, grace, or read_only), or any request while the account is being deleted. No plan check is involved — eligibility comes from the Team seat. The body includes a `message` with guidance.
- `404`: The folder is not in a workspace the token can read, or the target workspace is outside the token's grant.
- `429`: The token or authenticated user exceeded a 60 requests per minute rate limit.
- `500`: Unexpected server error, or the live membership lookup failed. Retry rather than discarding the token — this is never a revocation signal.

---

[API](https://skmtc.dev/mdflow/apis/mdflow-public-api.md) · [All operations](https://skmtc.dev/mdflow/apis/mdflow-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mdflow/apis/mdflow-public-api/revisions/3691fc5d1688?raw)