Pereiti prie pagrindinio turinio
tasks

Create /tasks

Create a task. Required: name. Optional: description, dates, status, type, priority, goal, assignees, followers, relation (rel_type + related_uuid), billable, organization, and custom fields. Returns record with the detail projection.

POST
/tasks
Authorizationstringheaderprivaloma

API key (Bearer token) created in Setup → API & MCP.

Turinys

application/json
assigneesstring[]

Assignee staff UUIDs.

billablestring

Whether the task is billable.

custom_fieldsobject[]

Custom field values by slug.

descriptionstring

Task description (HTML allowed).

due_datestring

Due date/time (ISO 8601).

end_datestring

End date/time (ISO 8601).

followersstring[]

Follower staff UUIDs.

goalstring

Task goal picklist value UUID.

namestringprivaloma

Task title.

organizationstring

Organization UUID.

prioritystring

Task priority: 1 = low, 2 = medium, 3 = high, 4 = urgent. The tasks_priorities picklist value UUID is accepted as well.

rel_typestring

Related entity type (e.g. lead, customer, project). client/clients are accepted as aliases for customer.

UUID of the related entity (requires rel_type).

start_datestring

Start date/time (ISO 8601).

statusstring

Task status picklist value UUID.

task_typestring

Task type picklist value UUID.

Atsakymas

application/json

Success

recordobject

Fields enabled for this documentation instance (projection enabled: feature, option, subdomain, closures) plus account-level form field visibility. Role- and user-level field overrides are not applied here, so an API key whose staff user has such overrides may receive fewer fields. A disabled field is omitted from the response object entirely; a present key with a null value means the record simply has no value.