POST
/tasks/{task_gid}/subtasksCreate a subtask
Creates a new subtask and adds it to an existing parent task. Supply the new subtask fields in the data block, including any supported followers, projects, tags, or workspace values. The response contains the complete record for the newly created subtask.
- RetriesRetries up to 2×, 500ms backoff, 30s timeout.
opt_fieldsarray<string>optional
A comma-separated list of subtask properties to include in the response, including `actual_time_minutes`, `approval_status`, `assigned_by`, `assigned_by.name`, `assignee`, and `assignee.name`, among others.
The new subtask details, provided in the data object.
dataobjectoptional
The properties of the subtask to create, including supported task fields and optional followers, projects, tags, or workspace values.
201Returns the complete record for the newly created subtask.
dataobjectoptional
400Returned when a parameter is missing or malformed.
errorsarray<object>optional
401Returned when a valid authentication token was not provided.
errorsarray<object>optional
403Returned when the authenticated user does not have access to the parent task or subtask operation.
errorsarray<object>optional
404Returned when the request does not specify a known action or the specified parent task does not exist.
errorsarray<object>optional
500Returned when a server-side problem prevents the subtask from being created.
errorsarray<object>optional
Error handling
A 400 is returned when a parameter is missing or malformed. A 401 is returned when you do not provide a valid authentication token, and a 403 is returned when the authenticated user lacks access to the parent task or subtask operation. A 404 indicates that the request path is not a known action or the specified parent task does not exist; a 500 indicates a server-side failure. The request also requires the tasks:write scope.