--- search: tags: - tasks - POST seo: description: >- Creates a new task (ticket) in the specified project. Tasks are the core work units in… Reference for the POST /tasks endpoint in the Leadtime Public API API. sidebar: badge: POST label: Create a new task title: Create a new task type: openapi-operation --- Creates a new task (ticket) in the specified project. Tasks are the core work units in Leadtime and represent actionable items that need to be completed. Each task belongs to a project, has a type (e.g., Feature, Bug), a status (e.g., New, In Progress), and can include assignments, deadlines, time estimates, custom fields, tags, and subtasks. The description field accepts HTML or Markdown format and will be automatically converted to the internal editor format. Project access is validated before task creation. Requires Tasks.create permission. Some fields are dynamically required by workspace and task-type configuration. The global OpenAPI schema shows the universal request shape, but it cannot mark every conditionally required field as required for every workspace. Before creating tasks, read task type metadata from GET /tasks/types or GET /administration/task-settings/types, find the selected typeId, and include every field listed in that type requiredFields. Standard fields such as summary and estimatedTime can be listed there, as well as task custom fields. The API still validates the final request and returns field-level 400 errors when configured requirements are missing. Assignment fields are project-scoped. assignedToId and accountableId must reference a Leadtime User.id that is assignable in the selected project: either a project user/member with access to that project, or the workspace Leadtime agent user. Read GET /projects/{id} and use its users array before assigning; if a workspace user is missing from the project, add them with PATCH /projects/{id} first.