Skip to main content
POST
Requires tasks:write and current workspace membership. A successful request returns 201 with the created task under data.
string
required
Task title, from 1 to 500 characters.
string
Task description, up to 100,000 characters.
string
A task-status slug defined in the workspace.
enum<string>
Priority for the task.
number
Start time as a Unix timestamp in milliseconds.
number
Due time as a Unix timestamp in milliseconds. When both dates are supplied, the start must not be later than the due date.
string
An existing parent task accessible to the key’s owner.
string[]
Up to 50 workspace auth-user IDs.
integer
Estimated effort in minutes; a positive integer.
string[]
Up to 10 record IDs to link at creation. This field is not accepted by the task update endpoint.
Optional fields can be omitted for a minimal task. Use real status slugs and auth-user IDs from Kato; the general public API does not expose a member directory or task-status list endpoint.
object
The created task, including its id. Response dates use ISO 8601, and some response names differ from write inputs: dueDate and estimatedTime. See the full response conventions.
The response example uses illustrative IDs and a workspace with a todo default status. Your workspace’s status configuration determines the returned slug. Task creation uses the same service as the app, including activity, notifications, workflow triggers, and integration behavior. A timeout can occur after a successful write; check the workspace before retrying a creation request.