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

# Update a note

> Partial update of a note — title, context, locales, thread add/remove, feature toggles. **Pro license required.**



## OpenAPI

````yaml /api-reference/tiro/openapi.json patch /tiro/notes/{note_id}
openapi: 3.1.0
info:
  title: Magic Meal Kits — Tiro API
  version: 1.0.0
  description: >-
    Upload audio to Tiro and manage meeting notes — transcripts, summaries,
    threads (folders), webhooks, and API keys — through your Magic Meal Kits
    server. Backs the **티로 Tiro (Magic Meal Kits)** Make.com app.


    Every endpoint requires a **Pro** license (a Basic key gets `400` `you are
    not a magic meal kits PRO user`). Auth uses the MMK `X-API-KEY` only; your
    Tiro token is set on the connection page in the Magic Meal Kits app and
    resolved server-side — no per-request token header is needed.


    This documents the MMK-proxy app only. The separate official-API-direct Tiro
    app (which calls `api.tiro.ooo` directly) is not covered here.
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
servers:
  - url: https://{deployment}/api/v1
    description: Your Magic Meal Kits deployment
    variables:
      deployment:
        default: magic-meal-kits-xxxxx.run.app
        description: Your Cloud Run host (without protocol)
security:
  - ApiKeyAuth: []
tags:
  - name: Upload
    description: Upload audio for transcription.
  - name: Notes
    description: Create, read, update, and delete meeting notes.
  - name: Content
    description: Transcripts and summaries.
  - name: Config
    description: Threads (folders) and supported locales.
  - name: Webhooks
    description: Subscribe to note events.
  - name: API keys
    description: Manage Tiro API keys.
paths:
  /tiro/notes/{note_id}:
    patch:
      tags:
        - Notes
      summary: Update a note
      description: >-
        Partial update of a note — title, context, locales, thread add/remove,
        feature toggles. **Pro license required.**
      operationId: tiroPatchNote
      parameters:
        - $ref: '#/components/parameters/NoteId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PatchNoteRequest'
            example:
              title: Renamed
              add_thread_ids:
                - 34
      responses:
        '200':
          description: Updated note
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NoteMutationResponse'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/TiroAuthError'
components:
  parameters:
    NoteId:
      name: note_id
      in: path
      required: true
      schema:
        type: integer
      description: >-
        Numeric Tiro note ID (not the note GUID — the handler parses it as an
        integer).
  schemas:
    PatchNoteRequest:
      type: object
      properties:
        title:
          type: string
        context:
          type: string
        transcribe_locale:
          type: string
        translate_locale:
          type: string
        summary_locale:
          type: string
        add_thread_ids:
          type: array
          items:
            type: integer
          description: Thread (folder) IDs to add the note to.
        enable_audio_replay:
          type: boolean
        enable_realtime_translation:
          type: boolean
        enable_enhanced_transcription:
          type: boolean
    NoteMutationResponse:
      type: object
      properties:
        success:
          type: boolean
        note_id:
          type: integer
        note_guid:
          type: string
        title:
          type: string
        note_url:
          type: string
        message:
          type: string
    ErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
  responses:
    BadRequest:
      description: >-
        Invalid request, or a Basic key on this Pro route (`you are not a magic
        meal kits PRO user`).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    TiroAuthError:
      description: >-
        Tiro connection not configured, or the stored token was rejected —
        (re)connect on the connection page.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY
      description: Your deployment's API key (MMK_API_KEY).

````