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

# Delete Telegram message

> Delete a message you sent (when the channel allows).



## OpenAPI

````yaml /en/telegram-api/api-reference/openapi-telegram.json delete /v1/telegram/messages/{messageId}
openapi: 3.0.3
info:
  title: Notifique API — Telegram
  description: >-
    Send Telegram messages and manage connections. Authenticate with
    `Authorization: Bearer sk_live_...` or `x-api-key`.
  version: 1.0.0
servers:
  - url: https://api.notifique.dev
    description: Production
security:
  - ntfTgBearerAuth: []
  - ntfTgApiKeyHeader: []
tags:
  - name: Messages
    description: Send and manage messages
  - name: Instances
    description: Create and connect bots or USER accounts
  - name: Chats
    description: List chats
paths:
  /v1/telegram/messages/{messageId}:
    delete:
      tags:
        - Mensagens
      summary: Delete Telegram message
      description: Delete a message you sent (when the channel allows).
      operationId: ntfTg_deleteV1TelegramMessage
      parameters:
        - name: messageId
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Status local atualizado para apagada.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NtfTg_MessageIdStatusResponse'
              example:
                success: true
                data:
                  messageId: clxx_msg
                  status: DELETED
        '400':
          description: >-
            No há ID no Telegram, message já apagada, instance inativa ou o
            Telegram recusou a operação.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NtfTg_ErrorResponse'
              example:
                success: false
                error: Bad Request
                message: Não há identificador do Telegram para apagar esta mensagem.
                code: BAD_REQUEST
        '401':
          description: Chave ausente ou inválida.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NtfTg_ErrorResponse'
              example:
                success: false
                error: Unauthorized
                message: Invalid or missing API Key
                code: UNAUTHORIZED
        '403':
          description: Sem escopo **telegram:delete** ou instance não permitida.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NtfTg_ErrorResponse'
              example:
                success: false
                error: Forbidden
                message: 'Missing scope: telegram:delete'
                code: FORBIDDEN
        '404':
          description: Message inexistente.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NtfTg_ErrorResponse'
              example:
                success: false
                error: Not Found
                message: Message not found
                code: NOT_FOUND
components:
  schemas:
    NtfTg_MessageIdStatusResponse:
      type: object
      properties:
        success:
          type: boolean
        data:
          type: object
          properties:
            messageId:
              type: string
            status:
              type: string
              enum:
                - DELETED
                - CANCELLED
                - EDITED
    NtfTg_ErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
          description: 'Rótulo HTTP do erro (ex.: Unauthorized, Bad Request, Not Found).'
        message:
          type: string
          description: >-
            Message legível para exibir ao usuário (localizada via
            Accept-Language / x-locale quando aplicável).
        code:
          type: string
          description: >-
            Código estável da API v1 (enum). Sempre presente em erros. Use com o
            status HTTP para decidir retry ou correção. Ver [Responses de
            erro](/guides/conceitos/resposta-de-erros).
        details:
          type: array
          items:
            type: object
            properties:
              field:
                type: string
              message:
                type: string
      required:
        - success
        - error
        - message
        - code
  securitySchemes:
    ntfTgBearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: 'Authorization: Bearer sk_live_xxxxx'
    ntfTgApiKeyHeader:
      type: apiKey
      in: header
      name: x-api-key

````