> ## 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 proposed corrections awaiting your decision

> **The caller's own** drafts, pending and resolved alike — the dismissed ones are what the analyser dedupes against, so a "no" only sticks while they are readable. The caller filters on `status`.

A user nothing has been proposed for returns an empty list, not an error. Subject: `microstrate.hub.get.coworker-correction-drafts`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json get /hub/coworker/correction-drafts
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/correction-drafts:
    get:
      tags:
        - Corrections
      summary: List proposed corrections awaiting your decision
      description: >-
        **The caller's own** drafts, pending and resolved alike — the dismissed
        ones are what the analyser dedupes against, so a "no" only sticks while
        they are readable. The caller filters on `status`.


        A user nothing has been proposed for returns an empty list, not an
        error. Subject: `microstrate.hub.get.coworker-correction-drafts`.
      operationId: getCoworkerCorrectionDrafts
      responses:
        '200':
          description: Draft list
          content:
            application/json:
              schema:
                type: object
                properties:
                  drafts:
                    type: array
                    items:
                      $ref: '#/components/schemas/CoworkerCorrectionDraft'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '502':
          $ref: '#/components/responses/UpstreamError'
components:
  schemas:
    CoworkerCorrectionDraft:
      type: object
      description: >-
        A proposed correction awaiting the person's decision. FROZEN
        cross-module record (docs/abbie-corrections-surface-plan.md §3) —
        mirrored by hand in bellerophon-workforce, which writes this same
        per-user document directly and cannot import hub. FIELD COUNT: 9.
        Nothing in this aggregate reaches any prompt until it is approved.
      properties:
        id:
          type: string
          description: Draft id, stamped by the filer
        status:
          type: string
          enum:
            - pending
            - approved
            - dismissed
            - expired
          description: >-
            Server-owned. Approved and dismissed drafts are immutable; a
            dismissal is permanent. Expired means it aged out unanswered and
            still accepts a late approve or dismiss.
          readOnly: true
        situation:
          type: string
          maxLength: 150
        instead:
          type: string
          maxLength: 200
        confidence:
          type: number
          format: double
          description: >-
            The analyser's confidence. Corrections never auto-apply at any
            confidence.
        evidence:
          type: string
          description: A verbatim quote from the user's own turn
        source:
          type: string
          enum:
            - analyser
            - vote
          description: >-
            Which feed filed it. Anything unrecognised is recorded as `analyser`
            on approval — never as `manual`, which would claim a person typed
            it.
        session_id:
          type: string
          description: Provenance
        created_at:
          type: string
          format: date-time
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - error
  responses:
    Unauthorized:
      description: No account (or user) identity in the auth context
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    UpstreamError:
      description: >-
        A backend read or write failed — deliberately not degraded to an empty
        or default answer
      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.