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

# Delete style guide rules

> Deletes style guide rules by their Developer IDs (from POST /styleguides/rules or GET /styleguides). This cannot be undone. The operation is all-or-nothing: if any ruleId does not exist, none are deleted.



## OpenAPI

````yaml openapi.json delete /styleguides/rules
openapi: 3.0.0
info:
  version: 1.0.0
  title: Ditto API
  description: Programmatically read and write data in your Ditto workspace.
servers:
  - url: https://api.dittowords.com/v2
security: []
paths:
  /styleguides/rules:
    delete:
      tags:
        - Style guides
      summary: Delete style guide rules
      description: >-
        Deletes style guide rules by their Developer IDs (from POST
        /styleguides/rules or GET /styleguides). This cannot be undone. The
        operation is all-or-nothing: if any ruleId does not exist, none are
        deleted.
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                ruleIds:
                  type: array
                  items:
                    type: string
                    minLength: 1
                  minItems: 1
                  description: >-
                    Developer IDs of the rules to delete (from POST
                    /styleguides/rules or GET /styleguides).
              required:
                - ruleIds
              example:
                ruleIds:
                  - be-concise
                  - ai-agent
      responses:
        '200':
          description: Returns success status of the deletion operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Indicates whether the deletion was successful
                required:
                  - success
                example:
                  success: true
        '400':
          description: >-
            Returned when the request body fails validation, for example an
            empty ruleIds array.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the validation failure
                required:
                  - message
              example:
                message: 'Invalid ''ruleIds'' input: Must have at least one rule ID.'
        '404':
          description: Returned when a ruleId does not match any rule in the workspace
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the validation failure
                required:
                  - message
              example:
                message: 'Rule id not found: missing-rule'
      security:
        - ApiKeyAuth: []
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization

````