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

# Delete a memory

> A tombstone upsert (`deleted: true`), not a stream delete — the retained text is what stops the consolidation consumer silently re-proposing a fact the user deleted.

`?purge=true` additionally drops the stored text, for memories captured automatically where "delete" meaning "hide, but keep what you said" is the wrong default. Subject: `microstrate.hub.delete.coworker-org-memory`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json delete /hub/coworker/org-memory/{id}
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/org-memory/{id}:
    delete:
      tags:
        - Memory
      summary: Delete a memory
      description: >-
        A tombstone upsert (`deleted: true`), not a stream delete — the retained
        text is what stops the consolidation consumer silently re-proposing a
        fact the user deleted.


        `?purge=true` additionally drops the stored text, for memories captured
        automatically where "delete" meaning "hide, but keep what you said" is
        the wrong default. Subject:
        `microstrate.hub.delete.coworker-org-memory`.
      operationId: deleteCoworkerOrgMemory
      parameters:
        - $ref: '#/components/parameters/MemoryIdPath'
        - $ref: '#/components/parameters/MemoryScope'
        - name: purge
          in: query
          required: false
          description: >-
            `true` also erases the stored memory text. Forwarded as
            `x-param-query-purge`.
          schema:
            type: string
            enum:
              - 'true'
              - 'false'
      responses:
        '200':
          $ref: '#/components/responses/SuccessMessage'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '502':
          $ref: '#/components/responses/UpstreamError'
components:
  parameters:
    MemoryIdPath:
      name: id
      in: path
      required: true
      description: Memory id. Forwarded as `x-param-id`.
      schema:
        type: string
    MemoryScope:
      name: scope
      in: query
      required: false
      description: >-
        `user` addresses the caller's personal memories; anything else resolves
        to organisation, so callers written before personal memories existed
        keep working unchanged. Forwarded as `x-param-query-scope`.
      schema:
        type: string
        enum:
          - organisation
          - user
        default: organisation
  responses:
    SuccessMessage:
      description: Success
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/SuccessMessage'
    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'
    NotFound:
      description: The addressed resource does not exist for this caller
      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'
  schemas:
    SuccessMessage:
      type: object
      properties:
        message:
          type: string
          example: success
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - 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.