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

# Disable monitoring

> Soft-deletes the config and stops logging. The Airtable Monitoring Base is left intact; the underlying Airtable subscription is only torn down if nothing else needs it.



## OpenAPI

````yaml /openapi.json delete /monitoring-config/{id}
openapi: 3.0.4
info:
  title: Simplified Webhooks Backend
  version: '1.0'
  description: >-
    API for Airtable webhooks, usage (record & attachment-storage counting), and
    change-monitoring audit logs.
  contact:
    name: API Support
    url: https://www.simplified-webhooks.com/contact-us
    email: contact@simplified-webhooks.com
servers:
  - url: https://api.simplified-webhooks.com
    description: Main server
security: []
tags:
  - name: Webhooks
    description: Register, update, and delete delivery webhooks for Airtable changes.
  - name: Usage
    description: >-
      Track daily record counts and attachment storage per Airtable base, and
      read the snapshot time-series.
  - name: Audit Log
    description: >-
      Configure change monitoring that logs every record & schema change into a
      Changes table in your own Airtable base.
paths:
  /monitoring-config/{id}:
    delete:
      tags:
        - Audit Log
      summary: Disable monitoring
      description: >-
        Soft-deletes the config and stops logging. The Airtable Monitoring Base
        is left intact; the underlying Airtable subscription is only torn down
        if nothing else needs it.
      operationId: deleteMonitoringConfig
      parameters:
        - $ref: '#/components/parameters/MonitoringConfigId'
      responses:
        '204':
          description: Monitoring disabled.
        '401':
          description: Unauthorized, authentication token is missing or invalid.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Monitoring config not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - apiKey: []
components:
  parameters:
    MonitoringConfigId:
      name: id
      in: path
      required: true
      description: The monitoring config id.
      schema:
        type: string
        format: uuid
        example: 8f1d6b2c-3a4e-4c5d-9e6f-0a1b2c3d4e5f
  schemas:
    ErrorResponse:
      type: object
      properties:
        message:
          type: string
          example: 'Missing required fields: [tableId, event]'
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: Authorization
      description: API key for authentication.

````