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

# List the caller's backlog (personal + organisation)

> Returns the account's org backlog first, then the caller's personal backlog, merged into one list and tagged with `scope`. There is no `user_id` parameter — personal scope is always the authenticated caller's own document. Subject: `microstrate.hub.get.coworker-todos`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json get /hub/coworker/todos
openapi: 3.1.0
info:
  title: Abbie API (beta)
  version: 1.0.0
  description: >
    **Beta.** This API is in beta: operations and fields may change without a
    deprecation period. Do not depend on undocumented fields. It covers the
    subset of Abbie's API used by the Quiva coworker MCP server: skills, todos,
    memory, profile, corrections, environment and models.


    HTTP surface of hub-service for Abbie/Coworker configuration, agent rapport
    & context, chat-session sharing, and MCP registration.


    ## Transport and response envelope


    Every operation here is a gateway mapping onto a Bellerophon/kraken subject
    of the form `microstrate.hub.<method>.<endpoint-slug>` (see
    `hub-service/service/service.go` and `docs/abbie-gateway-mappings.md`).
    Handlers reply on the mesh with an envelope `{"status_code": <int>, "body":
    <object>}`; the gateway unwraps it, so `status_code` becomes the HTTP status
    and `body` becomes the HTTP response body. **The schemas below describe the
    unwrapped `body`.**


    Errors are always `{"error": "<message>"}` with the matching HTTP status.


    ## Parameter conventions


    The gateway forwards URL parameters to the handler as request headers:


    - `x-param-query-<name>` — a query-string parameter (`?name=value`)

    - `x-param-<name>` — a path parameter


    Every parameter documented as `in: query` or `in: path` below corresponds to
    one of those headers, and the header suffix is named in each parameter's
    description where it is not obvious.


    ## Authentication


    All operations require the caller's bearer token; the account id, user id
    and user public key are always taken from the JWT and never from the URL or
    body. Endpoints that additionally require an account **admin** role are
    marked in their description — a failed role lookup answers **502**, never
    403 and never a pass.


    ## Two path notes


    - `PATCH /hub/agent-session-visibility/{session_id}` — the handler reads the
    path parameter as `x-param-session_id`, matching its sibling `PATCH
    /hub/agent-session/{session_id}`.

    - `GET|POST|PUT /hub/agent/user-context/{id}` — the handler requires the
    **agent id** as `x-param-id`; the frontend calls
    `/hub/agent/user-context/<agentId>`.
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Skills
  - name: Todos
  - name: Memory
  - name: Profile and personality
  - name: Corrections
  - name: Environment
  - name: Models
paths:
  /hub/coworker/todos:
    get:
      tags:
        - Todos
      summary: List the caller's backlog (personal + organisation)
      description: >-
        Returns the account's org backlog first, then the caller's personal
        backlog, merged into one list and tagged with `scope`. There is no
        `user_id` parameter — personal scope is always the authenticated
        caller's own document. Subject: `microstrate.hub.get.coworker-todos`.
      operationId: getCoworkerTodos
      parameters:
        - name: status
          in: query
          required: false
          description: Single status filter.
          schema:
            $ref: '#/components/schemas/TodoStatus'
        - name: session_id
          in: query
          required: false
          description: Only items raised from this chat session.
          schema:
            type: string
        - name: open_only
          in: query
          required: false
          description: '`true` restricts to open items.'
          schema:
            type: string
            enum:
              - 'true'
              - 'false'
        - name: scheduled
          in: query
          required: false
          description: '`true` restricts to items with a schedule armed.'
          schema:
            type: string
            enum:
              - 'true'
              - 'false'
      responses:
        '200':
          description: Merged backlog
          content:
            application/json:
              schema:
                type: object
                properties:
                  items:
                    type: array
                    items:
                      $ref: '#/components/schemas/TodoItem'
                  count:
                    type: integer
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    TodoStatus:
      type: string
      enum:
        - pending
        - in_progress
        - done
        - awaiting_user
        - cancelled
    TodoItem:
      type: object
      properties:
        id:
          type: string
        content:
          type: string
          description: The one-line item
        details:
          type: string
          description: Long-form context behind `content`
        status:
          $ref: '#/components/schemas/TodoStatus'
        owner_user_id:
          type: string
          description: Mesh identity of the item's owner
        session_id:
          type: string
        blocked_on:
          type: string
        follow_up_at:
          type: string
          format: date-time
          description: >-
            "Chase the person this item is parked on" — only meaningful on an
            `awaiting_user` item
        kind:
          type: string
        scheduled_for:
          type: string
          format: date-time
        cron:
          type: string
        created:
          type: string
          format: date-time
        updated:
          type: string
          format: date-time
        scope:
          type: string
          enum:
            - organisation
            - user
          description: Added by the read/write handlers; not part of the stored document
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - error
  responses:
    BadRequest:
      description: Malformed payload or a failed validation rule
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: No account (or user) identity in the auth context
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

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