> ## Documentation Index
> Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update a task

> Changes only the keys sent: the standard fields GET /v1/fields?object=task marks `writable` (title, description, status, priority, start_date, due_date and assignee, unless a sync in your workspace owns one) at the top level, and custom fields under `fields` (the task's type's, its project's and its own). `null` clears a field: `assignee` unassigns the task, `priority` unsets it, and an empty `description` clears it too; `title`, `status` and a mandatory custom field cannot be cleared. `status` is a status name, matched exactly, case included, from the task's own status template, as on a create. `assignee` is a user's person id or a contact of the task's account (a project task's: its project's account). `type`, `account`, `project` and `parent` are set at create and cannot change. The task may not start after it is due, by calendar day; a date sent alone is checked against the stored other one. In a project that cascades dates, the change carries through in the same write: moving the task's `start_date` moves its subtasks by the same amount; each task that depends on it is rescheduled to start the day after its latest blocker is due, keeping its length; each parent's `due_date` becomes the latest of its subtasks'; and the project's due date the latest of its tasks'. The answer shows only this task: read the others back to see where they moved. A task in a project synced from another tool takes custom fields only: a request with any standard field is a 409 and writes nothing. Every key is checked before anything is written. When a standard field changed, the task's followers who are users are then emailed, as in the app; custom values alone send nothing. A 500 whose `details` list fields as `written` means those standard fields were written and the custom values were not; it says whether to send them again or what refused them.



## OpenAPI

````yaml /api/statisfy-api.openapi.json patch /v1/objects/task/records/{task_id}
openapi: 3.1.0
info:
  description: >-
    The agent-first Statisfy API. Authenticate with an API key (`Authorization:
    Bearer stfy_live_…`), then call `GET /v1/meta/capabilities` to discover
    every operation and its schemas.
  title: Statisfy API
  version: 1.0.0
servers:
  - url: https://api.statisfy.com
    description: Production
security: []
paths:
  /v1/objects/task/records/{task_id}:
    patch:
      tags:
        - tasks
      summary: Update a task
      description: >-
        Changes only the keys sent: the standard fields GET
        /v1/fields?object=task marks `writable` (title, description, status,
        priority, start_date, due_date and assignee, unless a sync in your
        workspace owns one) at the top level, and custom fields under `fields`
        (the task's type's, its project's and its own). `null` clears a field:
        `assignee` unassigns the task, `priority` unsets it, and an empty
        `description` clears it too; `title`, `status` and a mandatory custom
        field cannot be cleared. `status` is a status name, matched exactly,
        case included, from the task's own status template, as on a create.
        `assignee` is a user's person id or a contact of the task's account (a
        project task's: its project's account). `type`, `account`, `project` and
        `parent` are set at create and cannot change. The task may not start
        after it is due, by calendar day; a date sent alone is checked against
        the stored other one. In a project that cascades dates, the change
        carries through in the same write: moving the task's `start_date` moves
        its subtasks by the same amount; each task that depends on it is
        rescheduled to start the day after its latest blocker is due, keeping
        its length; each parent's `due_date` becomes the latest of its
        subtasks'; and the project's due date the latest of its tasks'. The
        answer shows only this task: read the others back to see where they
        moved. A task in a project synced from another tool takes custom fields
        only: a request with any standard field is a 409 and writes nothing.
        Every key is checked before anything is written. When a standard field
        changed, the task's followers who are users are then emailed, as in the
        app; custom values alone send nothing. A 500 whose `details` list fields
        as `written` means those standard fields were written and the custom
        values were not; it says whether to send them again or what refused
        them.
      operationId: tasks_update
      parameters:
        - in: path
          name: task_id
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: true
              properties:
                assignee:
                  default: null
                  description: >-
                    A user's or a contact's person id: a user, or a contact of
                    the task's account (a project task's: its project's
                    account); null unassigns the task
                  title: Assignee
                  type: string
                description:
                  default: null
                  description: Free text
                  title: Description
                  type: string
                due_date:
                  default: null
                  description: YYYY-MM-DD
                  format: date
                  title: Due Date
                  type: string
                fields:
                  anyOf:
                    - additionalProperties: true
                      type: object
                    - type: 'null'
                  default: null
                  description: Custom field keys to values
                  title: Fields
                priority:
                  default: null
                  description: low, medium or high; null unsets it
                  enum:
                    - low
                    - medium
                    - high
                  title: Priority
                  type: string
                start_date:
                  default: null
                  description: YYYY-MM-DD
                  format: date
                  title: Start Date
                  type: string
                status:
                  default: null
                  description: A status name from the task's own status template
                  title: Status
                  type: string
                title:
                  default: null
                  description: The task's title
                  title: Title
                  type: string
              type: object
        required: false
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Task'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    Task:
      properties:
        account:
          anyOf:
            - type: string
            - type: 'null'
          description: The id of the account the task is on
          title: Account
        account_name:
          anyOf:
            - type: string
            - type: 'null'
          title: Account Name
        activity:
          anyOf:
            - type: string
            - type: 'null'
          description: The id of the activity the task came from
          title: Activity
        assignee:
          anyOf:
            - type: string
            - type: 'null'
          description: 'The assignee''s id: a person''s'
          title: Assignee
        assignee_name:
          anyOf:
            - type: string
            - type: 'null'
          title: Assignee Name
        assignee_type:
          anyOf:
            - enum:
                - user
                - contact
                - vendor
                - digital_worker
              type: string
            - type: 'null'
          description: >-
            user (a teammate), contact, vendor or digital_worker; null when
            unknown
          title: Assignee Type
        created_at:
          anyOf:
            - type: string
            - type: 'null'
          title: Created At
        creator:
          anyOf:
            - type: string
            - type: 'null'
          description: The id of the user who created the task
          title: Creator
        description:
          anyOf:
            - type: string
            - type: 'null'
          title: Description
        due_date:
          anyOf:
            - type: string
            - type: 'null'
          title: Due Date
        fields:
          additionalProperties: true
          title: Fields
          type: object
        id:
          title: Id
          type: string
        parent:
          anyOf:
            - type: string
            - type: 'null'
          description: The id of the parent task
          title: Parent
        priority:
          anyOf:
            - enum:
                - low
                - medium
                - high
              type: string
            - type: 'null'
          title: Priority
        project:
          anyOf:
            - type: string
            - type: 'null'
          description: The id of the project the task is in
          title: Project
        project_name:
          anyOf:
            - type: string
            - type: 'null'
          title: Project Name
        start_date:
          anyOf:
            - type: string
            - type: 'null'
          title: Start Date
        status:
          anyOf:
            - type: string
            - type: 'null'
          title: Status
        status_group:
          anyOf:
            - enum:
                - not_started
                - active
                - done
                - archived
              type: string
            - type: 'null'
          title: Status Group
        title:
          anyOf:
            - type: string
            - type: 'null'
          title: Title
        type:
          anyOf:
            - enum:
                - activity_task
                - risk_mitigation
                - expansion
                - key_next_step
                - escalation
                - project
                - milestone
              type: string
            - type: 'null'
          title: Type
        updated_at:
          anyOf:
            - type: string
            - type: 'null'
          title: Updated At
      required:
        - id
      title: Task
      type: object
  securitySchemes:
    HTTPBearer:
      scheme: bearer
      type: http
      description: >-
        An API key, sent as `Authorization: Bearer stfy_live_…`. See
        [Authentication](/rest-api/authentication) for how to get one and which
        scopes it needs.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.