Skip to main content
POST
Create a card

Authorizations

Authorization
string
header
default:dav_ak_live_your_token
required

Personal access token. The scopes granted at issuance determine both which operations the key may call and the ceiling on the resource permissions it can exercise. Each scope family is a ladder: projects:manage implies projects:write and projects:read; cards:manage implies cards:write and cards:read; and teams:manage implies teams:write and teams:read. These are named API capability bundles, not blanket domain roles: manage exposes only the permissions enumerated for that scope and never bypasses the acting user's current role-based access.

Headers

Idempotency-Key
string

A value you choose to identify this request, so that retrying it does not repeat its effect. Reuse the same key when retrying and the original result is returned; use a fresh key when you mean to create something new. Keys are scoped to the API key that sent them (or to the user for browser sessions). Replayed responses include Idempotency-Replayed: true.

Maximum string length: 255

Path Parameters

projectId
string
required

Project id. May be compound in the form {projectId}--{branchName}.

Minimum string length: 1

Body

application/json
name
string
required

Sanitized by the server to a resource name of at most 255 characters.

description
string | null
resolution
string | null
Maximum string length: 10000
isOpen
boolean
default:true
deadline
string<date-time> | null
effort
integer | null
Required range: x >= 0
assigneeId
string<uuid>

Optional initial assignee. The server validates current Project membership and creates the Card, assignment, and both history entries in one transaction.

Response

Card created.

card
object
required
historyHeadId
string<uuid> | null
required

Latest committed card-history row ID; null only before a card has history.

historyHeadSequence
string | null
required

Globally monotonic card-history sequence.

Pattern: ^\d+$
indexCard
object | null