# POST /api/v2/workflows

Create a workflow

- MCP id: workflows.store
- Scope: api:write:workflows
- Permission: workflows::create
- Needs the sprints feature on your organisation
- Rate cost: 1 unit, write bucket. A write costs the same whatever `view` you ask for.
- Cache-Control: private, no-store

Creates a workflow and returns it with a `Location` header.

`name` is the only accepted field: `order` is not writable, so the new workflow is created at position 0 and is reordered only by dragging it in plnnrly. The workflow is created empty (with zero statuses and zero transitions), because statuses and transitions are separate collections: `POST /api/v2/workflow-statuses` with `workflow_id` for each status, then POST `/api/v2/workflow-transitions` to connect them. That sequence is not atomic, so a client that fails partway leaves a workflow with an incomplete status set, and a project pointed at it cannot move work items along the missing transitions.

## Parameters
- view (string, optional): Which field set to render.
- X-Request-Id (header, optional): A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
- Idempotency-Key (header, optional): A caller-chosen key that makes this POST safe to retry. Replaying it returns the original response with Idempotency-Replayed: true.

## Request body
- name (string ≤ 255, required): Workflow name as shown in the UI, e.g. `Standard`.

Unknown keys are refused with `422` validation-failed, naming the key.

## Response 201
- id (integer, required): Unique identifier.
- name (string ≤ 255, required): Workflow name as shown in the UI, e.g. `Standard`.
- order (integer, required, server-assigned): Display position; set by dragging in plnnrly and not writable. API-created workflows are created at 0 and fall back to the id tiebreaker.
- created_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Creation timestamp.
- updated_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Last-write timestamp; use for incremental sync.
- statuses_count (integer ≥ 0, required): Number of statuses in this workflow.
- links (WorkflowLinks, required)
  - self (url, required): The canonical URI of this record.
  - statuses (url, required): Statuses in this workflow, in workflow order.

## Errors
- 403 forbidden-by-policy | insufficient-permission | insufficient-token-scope: Forbidden.
- 409 idempotency-key-in-flight | idempotency-key-reused: Conflict.
- 415 unsupported-media-type: Unsupported media type.
- 422 unprocessable-relationship | validation-failed: Unprocessable content.
- 400 idempotency-key-required | invalid-cursor | invalid-query-parameter | malformed-request | unsupported-parameter: Bad request.
- 401 token-expired | unauthenticated: Unauthenticated.
- 404 endpoint-not-found | resource-not-found: Not found.
- 406 not-acceptable: Not acceptable.
- 429 rate-limit-exceeded: Too many requests.
- 500 internal-error: Server error.
- 503 tenant-unavailable: Service unavailable.

## Example
```bash
curl -X POST \
  'https://<your-url>/api/v2/workflows' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <key>' \
  -d '{
    "name": "Bug triage"
  }'
```