> ## 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.

# Create a task

> Creates a task and returns it with 201: the app's own create. `title` is required, and the task is on an `account` (a live account's id) or in a `project` (a project's id; the task is then on the project's account, and `account` may be left out). `type` defaults to activity_task; a task in a project may also be a project or milestone, and its `parent` may name a task in the same project (a milestone takes none), while a task on an account takes any type but those two. `status` is a status name, matched exactly, from the task's status template, the one the app's status picker offers for it: a project's tasks use the project's template, else its project template's, else the global one; other tasks use their type's, else the global one. When not sent, the API picks that template's TODO status, else its first not-started one. `assignee` is a user's id or a contact of the task's account; with none, the task is unassigned. A person's own key (the MCP server's connection) makes that person the task's `creator`; an org key makes no one. `priority` (low, medium or high), `start_date` and `due_date` (YYYY-MM-DD, start not after due), `description` and custom fields under `fields` are optional; the custom fields are those of the task's type and of its project. Every key is checked before anything is written, and any problem refuses the whole request with a 422 listing each one in `details`. A project synced from another tool (Jira, Wrike, Linear, Rocketlane) manages its tasks: creating one in it is a 409, ahead of any other problem. As in the app, an assigned user is then emailed (a contact is not). A 500 that says the task was created, or may have been, names it in `details` (`task_ids`): do not create it again. Send an `Idempotency-Key` header to make a retry safe: the same key replays the first answer, including such a 500.



## OpenAPI

````yaml /api/statisfy-api.openapi.json post /v1/objects/task/records
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:
    post:
      tags:
        - tasks
      summary: Create a task
      description: >-
        Creates a task and returns it with 201: the app's own create. `title` is
        required, and the task is on an `account` (a live account's id) or in a
        `project` (a project's id; the task is then on the project's account,
        and `account` may be left out). `type` defaults to activity_task; a task
        in a project may also be a project or milestone, and its `parent` may
        name a task in the same project (a milestone takes none), while a task
        on an account takes any type but those two. `status` is a status name,
        matched exactly, from the task's status template, the one the app's
        status picker offers for it: a project's tasks use the project's
        template, else its project template's, else the global one; other tasks
        use their type's, else the global one. When not sent, the API picks that
        template's TODO status, else its first not-started one. `assignee` is a
        user's id or a contact of the task's account; with none, the task is
        unassigned. A person's own key (the MCP server's connection) makes that
        person the task's `creator`; an org key makes no one. `priority` (low,
        medium or high), `start_date` and `due_date` (YYYY-MM-DD, start not
        after due), `description` and custom fields under `fields` are optional;
        the custom fields are those of the task's type and of its project. Every
        key is checked before anything is written, and any problem refuses the
        whole request with a 422 listing each one in `details`. A project synced
        from another tool (Jira, Wrike, Linear, Rocketlane) manages its tasks:
        creating one in it is a 409, ahead of any other problem. As in the app,
        an assigned user is then emailed (a contact is not). A 500 that says the
        task was created, or may have been, names it in `details` (`task_ids`):
        do not create it again. Send an `Idempotency-Key` header to make a retry
        safe: the same key replays the first answer, including such a 500.
      operationId: tasks_create
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: true
              description: >-
                A create body in the task's own shape: standard keys at the top
                level, custom

                keys under ``fields``. ``title`` and one of ``account`` /
                ``project`` are required.
              properties:
                account:
                  default: null
                  description: >-
                    The id of the account the task is on; a task in a project is
                    on the project's account
                  title: Account
                  type: string
                assignee:
                  default: null
                  description: A user's id, or a contact of the task's account
                  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
                parent:
                  default: null
                  description: The id of the parent task, in the same project
                  title: Parent
                  type: string
                priority:
                  default: null
                  description: low, medium or high
                  enum:
                    - low
                    - medium
                    - high
                  title: Priority
                  type: string
                project:
                  default: null
                  description: The id of the project the task is in
                  title: Project
                  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; its TODO
                    (else first not-started) status when not sent
                  title: Status
                  type: string
                title:
                  default: null
                  description: 'Required: the task''s title'
                  title: Title
                  type: string
                type:
                  default: null
                  description: >-
                    activity_task (the default, as the app creates tasks), or
                    for a task in a project also project or milestone; a task on
                    an account takes any type but project and milestone
                  enum:
                    - activity_task
                    - risk_mitigation
                    - expansion
                    - key_next_step
                    - escalation
                    - project
                    - milestone
                  title: Type
                  type: string
              type: object
        required: false
      responses:
        '201':
          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.