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

# Forget a fact

> Delete one fact. Deletes are never refused for quota reasons.



## OpenAPI

````yaml /openapi.json delete /v1/memory/{memoryId}
openapi: 3.0.3
info:
  title: Zavu Unified Messaging Layer API
  version: 0.2.0
  description: >
    Unified multi-channel messaging API for Zavu.


    Supported channels:

    - **SMS**: Simple text messages

    - **WhatsApp**: Rich messaging with media, buttons, lists, CTA URL buttons,
    location requests, and templates

    - **Telegram**: Bot messaging with text, media, and interactive elements

    - **Email**: Transactional emails via Amazon SES


    Design goals:

    - Simple `send()` entrypoint for developers

    - Project-level authentication via Bearer token

    - Support for all WhatsApp message types (text, image, video, audio,
    document, sticker, location, contact, buttons, list, cta_url,
    location_request, reaction, template)

    - If a non-text message type is sent, WhatsApp channel is used automatically

    - 24-hour WhatsApp conversation window enforcement

    - Universal `to` field accepts phone numbers (E.164), email addresses, or
    numeric chat IDs (Telegram/Instagram/Messenger)
servers:
  - url: https://api.zavu.dev
security:
  - bearerAuth: []
paths:
  /v1/memory/{memoryId}:
    delete:
      tags:
        - Memory
      summary: Forget a fact
      description: Delete one fact. Deletes are never refused for quota reasons.
      operationId: deleteMemory
      parameters:
        - $ref: '#/components/parameters/MemoryIdParam'
        - $ref: '#/components/parameters/MemoryScopeParam'
      responses:
        '204':
          description: Fact deleted.
        '401':
          description: Unauthorized.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: No such fact in that scope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - bearerAuth: []
components:
  parameters:
    MemoryIdParam:
      name: memoryId
      in: path
      required: true
      description: Memory (fact) ID.
      schema:
        type: string
    MemoryScopeParam:
      name: scope
      in: query
      required: false
      description: >-
        Which scope to address: `contact:<contactId>`,
        `conversation:<conversationId>`, or omitted for the project scope.


        Note the asymmetry with `POST /v1/memory` and `POST /v1/memory/search`,
        which take the scope in the request BODY as `scope` plus
        `contactId`/`conversationId`. Every other Memory endpoint takes it here.
      schema:
        $ref: '#/components/schemas/MemoryScopeQuery'
  schemas:
    Error:
      type: object
      required:
        - code
        - message
      properties:
        code:
          type: string
          example: invalid_request
        message:
          type: string
          example: Phone number is invalid
        details:
          type: object
          additionalProperties: true
    MemoryScopeQuery:
      type: string
      description: >-
        Scope as a query-string value: `contact:<contactId>`,
        `conversation:<conversationId>`, the literal `project`, or omitted for
        project scope.


        Only the SHAPE of the id is validated, never its existence — the
        partition already carries your project, so an id that matches nothing
        simply addresses an empty scope rather than returning 404.
      example: contact:jd7x2k3m4n5p6q7r8s9t0abc
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````