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

# Delete a monitor

> Delete a monitor, its run history, and its stored state.

Deleting a monitor removes its run history and stored state, and stops scheduling new runs. The response identifies the deleted monitor with `deleted: true`.

```bash cURL theme={null}
curl --request DELETE "https://api.perplexity.ai/v1/monitors/$MONITOR_ID" \
  --header "Authorization: Bearer $PERPLEXITY_API_KEY" | jq
```


## OpenAPI

````yaml delete /v1/monitors/{monitor_id}
openapi: 3.1.0
info:
  title: Perplexity AI API
  description: Perplexity AI API
  version: 1.0.0
servers:
  - url: https://api.perplexity.ai
    description: Perplexity AI API
security: []
paths:
  /v1/monitors/{monitor_id}:
    delete:
      tags:
        - Monitors
      summary: Delete a monitor
      description: >-
        Deletes the monitor, its run history, and its state, and stops
        scheduling new runs.
      operationId: deleteMonitor
      parameters:
        - $ref: '#/components/parameters/MonitorId'
      responses:
        '200':
          description: The deleted monitor id
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteMonitorResponse'
        '401':
          $ref: '#/components/responses/MonitorUnauthorized'
        '403':
          $ref: '#/components/responses/MonitorForbidden'
        '404':
          $ref: '#/components/responses/MonitorNotFound'
        '429':
          $ref: '#/components/responses/MonitorTooManyRequests'
        '502':
          $ref: '#/components/responses/MonitorBadGateway'
        '503':
          $ref: '#/components/responses/MonitorUnavailable'
        '504':
          $ref: '#/components/responses/MonitorGatewayTimeout'
      security:
        - HTTPBearer: []
      servers:
        - url: https://api.perplexity.ai
          description: Production API
components:
  parameters:
    MonitorId:
      name: monitor_id
      in: path
      required: true
      schema:
        type: string
      description: Monitor identifier (mon_...)
  schemas:
    DeleteMonitorResponse:
      type: object
      required:
        - id
        - object
        - deleted
      properties:
        id:
          type: string
        object:
          type: string
          enum:
            - monitor
        deleted:
          type: boolean
    MonitorApiError:
      type: object
      properties:
        error:
          type: object
          required:
            - message
            - type
            - code
          properties:
            message:
              description: Human-readable error message
              type: string
            type:
              $ref: '#/components/schemas/MonitorApiErrorType'
            code:
              type: integer
              description: HTTP status code
            param:
              type: string
              description: Parameter that caused the error
    MonitorApiErrorType:
      type: string
      enum:
        - invalid_request
        - invalid_api_key
        - token_expired
        - insufficient_quota
        - payment_required
        - forbidden
        - api_product_not_allowed
        - not_found
        - invalid_state
        - conflict
        - quota_exceeded
        - run_in_progress
        - request_rate_limit_exceeded
        - internal_error
        - bad_gateway
        - service_unavailable
        - gateway_timeout
      description: >
        Machine-readable error type. Monitors returns `invalid_request`

        (400), `invalid_api_key`, `token_expired` and

        `insufficient_quota` (401), `payment_required` (402),

        `forbidden` and `api_product_not_allowed` (403), `not_found`

        (404), `invalid_state` (409: the monitor's state does not allow

        the request; change it first), `conflict` (409: the monitor was

        modified concurrently; retry), `quota_exceeded` (409),

        `run_in_progress` (409), `request_rate_limit_exceeded` (429),

        `internal_error` (500), `bad_gateway` (502), `service_unavailable` (503)
        and

        `gateway_timeout` (504). New types may be added; act on `code`

        for an unknown one.
  responses:
    MonitorUnauthorized:
      description: Invalid API key, expired token, or no credits
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
    MonitorForbidden:
      description: Monitors are not available to this API Group
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
    MonitorNotFound:
      description: Monitor not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
    MonitorTooManyRequests:
      description: Rate limit exceeded
      headers:
        Retry-After:
          $ref: '#/components/headers/MonitorRetryAfter'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
    MonitorBadGateway:
      description: The Monitor request failed; retry.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
    MonitorUnavailable:
      description: Monitor service unavailable; retry
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
    MonitorGatewayTimeout:
      description: The monitor service did not answer in time; retry
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/MonitorApiError'
  headers:
    MonitorRetryAfter:
      schema:
        type: integer
        minimum: 1
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer

````