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

# List tasks

> Pages through tasks in a stable order. Filter with `filter[<key>][<op>]=<value>` (conditions are ANDed; `in` and `nin` repeat the parameter). Operators: eq, gt, gte, lt, lte, in, nin, contains, starts_with, exists, not_exists. The fields that can be filtered on are `id`, `title`, `type`, `status`, `priority`, `start_date`, `due_date`, `created_at`, `updated_at`, `account`, `project`, `parent`, `assignee` and custom fields; each accepts a subset of the operators, and anything else is a 422 naming what that field supports. `status_group` cannot be filtered on yet: filter `status` by the names in the group. Text `eq`, `contains` and `starts_with` ignore case, except on ids (`id`, `account`, `project`, `parent`, `assignee`), which match exactly; `in` and `nin` match exactly, except on `type` and `priority`, which take the values a record shows in any case. A project id no project can have is a 422. Dates are YYYY-MM-DD and compare as whole days. Standard fields sit at the top level and custom fields under `fields`, keyed as GET /v1/fields?object=task lists them. A task's name is `title` (there is no `name`). `type` is activity_task, risk_mitigation, expansion, key_next_step, escalation, project or milestone. `status` is the status's name and `status_group` its group: not_started, active, done or archived, or null when the status has none. `priority` is low, medium or high, or null when not set. `account` holds an account's id and `account_name` its name; `project` a project's id and `project_name` its title; `parent` the parent task's id; `activity` the activity the task came from. `assignee` holds a person's id and `assignee_name` their name; `assignee_type` is `user`, `contact`, `vendor` or `digital_worker`. A task with several assignees shows the earliest, and an `assignee` filter matches any of them. `creator` holds a user's id. Dates are YYYY-MM-DD; `created_at` and `updated_at` are their UTC day. Deleted tasks are never returned, nor customer goals, feature requests, issues and cancellations, which integrations and Statisfy's own processing write.



## OpenAPI

````yaml /api/statisfy-api.openapi.json get /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:
    get:
      tags:
        - tasks
      summary: List tasks
      description: >-
        Pages through tasks in a stable order. Filter with
        `filter[<key>][<op>]=<value>` (conditions are ANDed; `in` and `nin`
        repeat the parameter). Operators: eq, gt, gte, lt, lte, in, nin,
        contains, starts_with, exists, not_exists. The fields that can be
        filtered on are `id`, `title`, `type`, `status`, `priority`,
        `start_date`, `due_date`, `created_at`, `updated_at`, `account`,
        `project`, `parent`, `assignee` and custom fields; each accepts a subset
        of the operators, and anything else is a 422 naming what that field
        supports. `status_group` cannot be filtered on yet: filter `status` by
        the names in the group. Text `eq`, `contains` and `starts_with` ignore
        case, except on ids (`id`, `account`, `project`, `parent`, `assignee`),
        which match exactly; `in` and `nin` match exactly, except on `type` and
        `priority`, which take the values a record shows in any case. A project
        id no project can have is a 422. Dates are YYYY-MM-DD and compare as
        whole days. Standard fields sit at the top level and custom fields under
        `fields`, keyed as GET /v1/fields?object=task lists them. A task's name
        is `title` (there is no `name`). `type` is activity_task,
        risk_mitigation, expansion, key_next_step, escalation, project or
        milestone. `status` is the status's name and `status_group` its group:
        not_started, active, done or archived, or null when the status has none.
        `priority` is low, medium or high, or null when not set. `account` holds
        an account's id and `account_name` its name; `project` a project's id
        and `project_name` its title; `parent` the parent task's id; `activity`
        the activity the task came from. `assignee` holds a person's id and
        `assignee_name` their name; `assignee_type` is `user`, `contact`,
        `vendor` or `digital_worker`. A task with several assignees shows the
        earliest, and an `assignee` filter matches any of them. `creator` holds
        a user's id. Dates are YYYY-MM-DD; `created_at` and `updated_at` are
        their UTC day. Deleted tasks are never returned, nor customer goals,
        feature requests, issues and cancellations, which integrations and
        Statisfy's own processing write.
      operationId: tasks_list
      parameters:
        - description: >-
            Custom field keys to return (comma-separated); all of them when
            omitted
          explode: false
          in: query
          name: fields
          required: false
          schema:
            anyOf:
              - items:
                  type: string
                type: array
              - type: 'null'
            default: null
          style: form
        - in: query
          name: limit
          required: false
          schema:
            default: 25
            maximum: 100
            minimum: 1
            type: integer
        - description: '`next_cursor` from the previous page'
          in: query
          name: cursor
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            default: null
        - description: >-
            Filter with query parameters ``filter[<key>][<op>]=<value>``, all
            ANDed; ``in``

            and ``nin`` take the parameter repeated. Keys are those GET
            /v1/fields?object=task lists.


            Operators: `eq`, `neq`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`,
            `contains`, `not_contains`, `starts_with`, `ends_with`, `exists`,
            `not_exists`.
          explode: true
          in: query
          name: filter
          required: false
          schema:
            additionalProperties:
              additionalProperties: true
              type: object
            type: object
          style: deepObject
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TaskPage'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    TaskPage:
      properties:
        data:
          items:
            $ref: '#/components/schemas/Task'
          title: Data
          type: array
        has_more:
          default: false
          title: Has More
          type: boolean
        next_cursor:
          anyOf:
            - type: string
            - type: 'null'
          title: Next Cursor
      required:
        - data
      title: TaskPage
      type: object
    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.