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

# Update task

> Update an existing task.

Responses include direct Enginy app URLs when available. Responses include an `appUrl` that opens the updated task in Enginy. MCP agents should return those URLs to users whenever they are present in the response.

    > **Required scope:** `TASKS_WRITE`
    >
    > **Rate limit:** 30 requests per minute



## OpenAPI

````yaml https://openapi.enginy.ai/definitions.json patch /v1/tasks/{taskId}
openapi: 3.1.0
info:
  title: Enginy API
  version: 1.0.0
  description: Public API for Enginy platform
servers:
  - url: https://openapi.enginy.ai
    description: Configured server
security: []
tags:
  - name: AI Variables
    description: >-
      Manage AI variables and discover the entity fields you can reference in
      prompts and entity requests.
  - name: Inbox
    description: >-
      Inbox endpoints for listing contact threads, reading thread messages,
      managing tags, and sending manual replies.
  - name: Workflows
    description: >-
      Build, validate, publish, run, and inspect advanced (graph) workflows,
      plus the block/condition catalog needed to author a workflow plan.
paths:
  /v1/tasks/{taskId}:
    patch:
      tags:
        - Tasks
      summary: Update task
      description: >-
        Update an existing task.


        Responses include direct Enginy app URLs when available. Responses
        include an `appUrl` that opens the updated task in Enginy. MCP agents
        should return those URLs to users whenever they are present in the
        response.

            > **Required scope:** `TASKS_WRITE`
            >
            > **Rate limit:** 30 requests per minute
      parameters:
        - schema:
            type: string
            pattern: ^\d+$
          required: true
          name: taskId
          in: path
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                subject:
                  type: string
                description:
                  type:
                    - string
                    - 'null'
                assignedId:
                  type:
                    - integer
                    - 'null'
                  exclusiveMinimum: 0
                notes:
                  type:
                    - string
                    - 'null'
                ownerId:
                  type:
                    - string
                    - 'null'
                dueDate:
                  type: string
                priority:
                  type:
                    - string
                    - 'null'
                  enum:
                    - LOW
                    - MEDIUM
                    - HIGH
                    - null
      responses:
        '200':
          description: Task updated successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - success
                  message:
                    type: string
                  data:
                    type: object
                    properties:
                      success:
                        type: boolean
                        enum:
                          - true
                      appUrl:
                        type: string
                        format: uri
                    required:
                      - success
                      - appUrl
                required:
                  - status
                  - message
                  - data
      security:
        - apiKey: []
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key

````