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

# Delete Monitored Topics

> Permanently deletes one or more Monitored Topics. Topics not listed are left unchanged. Returns one result per requested id, in request order, with the reason for any id that was not deleted. Cascade per deleted topic: (1) any Topic campaign bound to this topic loses the binding — the binding is soft-deleted and the campaign's keyword set is regenerated automatically; (2) Prospects campaigns that use this topic in `commenting.postFilters.monitoredTopicIds` are NOT auto-cleaned — the id stays in the filter array but will no longer match anything, and the campaign must be updated if the filter should reflect the change.



## OpenAPI

````yaml https://api.goextrovert.com/client/v2/docs-json delete /client/v2/monitored-topics
openapi: 3.1.0
info:
  title: Extrovert Client API
  description: >-
    Public API for Extrovert platform integration. Use your API key for
    authentication.
  version: '1.0'
  contact: {}
servers:
  - url: https://api.goextrovert.com/
    description: API Server
security: []
tags: []
paths:
  /client/v2/monitored-topics:
    delete:
      tags:
        - Monitored Topics
      summary: Delete Monitored Topics
      description: >-
        Permanently deletes one or more Monitored Topics. Topics not listed are
        left unchanged. Returns one result per requested id, in request order,
        with the reason for any id that was not deleted. Cascade per deleted
        topic: (1) any Topic campaign bound to this topic loses the binding —
        the binding is soft-deleted and the campaign's keyword set is
        regenerated automatically; (2) Prospects campaigns that use this topic
        in `commenting.postFilters.monitoredTopicIds` are NOT auto-cleaned — the
        id stays in the filter array but will no longer match anything, and the
        campaign must be updated if the filter should reflect the change.
      operationId: RelevantPostTagClientApiController_delete
      parameters:
        - description: >-
            Permanently delete these topics independently. For each bound topic,
            detach its binding and reject that binding's pending-approval posts;
            hide bindings with history, physically remove empty ones. Prospect
            topic-filter arrays are not cleaned automatically.
          required: true
          name: ids
          in: query
          schema:
            minItems: 1
            maxItems: 25
            type: array
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteResponseDto6'
        '401':
          description: Invalid or missing API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClientApiErrorResponseDto'
      security:
        - api-key: []
components:
  schemas:
    DeleteResponseDto6:
      type: object
      properties:
        status:
          type: string
          const: success
          description: Response status
        data:
          type: array
          items:
            type: object
            properties:
              index:
                type: integer
                minimum: 0
                maximum: 9007199254740991
                description: Position of the element in the request list, starting at 0.
              id:
                description: >-
                  Element ID. Present for every updated or deleted element, and
                  for a created element once it was saved.
                type: string
                format: uuid
              error:
                description: >-
                  Why this element was not applied. Absent when the element
                  succeeded; the other elements are unaffected.
                type: object
                properties:
                  code:
                    type: string
                    description: >-
                      Status name of the failure, e.g. `NOT_FOUND`,
                      `PERMISSION_DENIED`, `INVALID_ARGUMENT`, `INTERNAL`.
                  message:
                    type: string
                    description: Human-readable reason this element was not applied.
                required:
                  - code
                  - message
            required:
              - index
          description: One result per requested id, in request order.
        message:
          type: string
          description: Success message
          examples:
            - Operation completed successfully
      required:
        - status
        - data
        - message
    ClientApiErrorResponseDto:
      type: object
      properties:
        status:
          type: string
          description: Response status
          example: error
          enum:
            - error
        data:
          type: object
          description: Response data
          example: null
          nullable: true
        message:
          type: string
          description: Error message
          example: An error occurred while processing the request
      required:
        - status
        - data
  securitySchemes:
    api-key:
      type: apiKey
      in: header
      name: X-API-Key
      description: API Key for authentication

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.