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

# List violation definitions

> List all available violation types and their configurations.



## OpenAPI

````yaml /openapi/em-data-readiness-v2.yaml get /api/data-readiness/violations/definitions
openapi: 3.1.0
info:
  title: EM Data Readiness Service
  description: Data Readiness Service API for managing workflows, metrics, and data quality
  version: 4.3.0-dev1
servers: []
security:
  - BearerAuth: []
tags:
  - name: Health
    description: Service health monitoring. Check service status and version information.
  - name: Root
    description: Root endpoint providing service information and navigation links.
  - name: Configuration
    description: Service configuration endpoints. View current configuration values.
  - name: Workflows
    description: >-
      Workflow configuration and execution management. Create, configure, and
      run data quality workflows including definitions, configurations, runs,
      and tasks.
  - name: Data Assets
    description: >-
      Data catalog entity management. Manage databases, schemas, and tables
      metadata.
  - name: Metrics
    description: >-
      Data quality metrics and scorecards. Calculate scores, view trends, and
      analyze dimensions.
  - name: Violations
    description: >-
      Data quality violation management. View, acknowledge, and remediate
      detected violations.
  - name: Glossary
    description: >-
      Business glossary management. Create, verify, and organize business terms
      and definitions.
paths:
  /api/data-readiness/violations/definitions:
    get:
      tags:
        - Violations
      summary: List violation definitions
      description: List all available violation types and their configurations.
      operationId: list_violation_definitions
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ViolationDefinitionListResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - BearerAuth: []
components:
  schemas:
    ViolationDefinitionListResponse:
      properties:
        definitions:
          items:
            $ref: '#/components/schemas/ViolationDefinitionResponse'
          type: array
          title: Definitions
          description: List of violation definitions
        total:
          type: integer
          title: Total
          description: Total number of definitions
          examples:
            - 37
      type: object
      required:
        - definitions
        - total
      title: ViolationDefinitionListResponse
      description: Response model for listing violation definitions.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ErrorResponse:
      properties:
        error:
          $ref: '#/components/schemas/ErrorInfo'
          description: >-
            Error information object containing code, message, and optional
            details
        request_id:
          anyOf:
            - type: string
            - type: 'null'
          title: Request Id
          description: Request ID for debugging and support
          examples:
            - req_abc123xyz
      type: object
      required:
        - error
      title: ErrorResponse
      description: >-
        Standard error response model for API errors.


        Matches the structure returned by _handle_service_error in
        workflows/routes.py.

        The actual API response format is:

        {
            "error": {
                "code": "ERROR_CODE",
                "message": "Error message",
                "details": {...}
            },
            "request_id": "optional-request-id"
        }
    ViolationDefinitionResponse:
      properties:
        id:
          type: string
          format: uuid
          title: Id
          description: Definition identifier
          examples:
            - 550e8400-e29b-41d4-a716-446655440010
        name:
          type: string
          title: Name
          description: Violation type name
          examples:
            - missing_description
        fqn:
          type: string
          title: Fqn
          description: Fully qualified name
          examples:
            - violations.missing_description
        display_name:
          anyOf:
            - type: string
            - type: 'null'
          title: Display Name
          description: Human-readable name
          examples:
            - Missing Description
        description:
          anyOf:
            - type: string
            - type: 'null'
          title: Description
          description: Description of what this violation means
          examples:
            - Triggered when a column lacks a description
        dimension:
          $ref: '#/components/schemas/DimensionRef'
          description: Reference to the assessment dimension
        default_severity:
          type: string
          title: Default Severity
          description: Default severity level
          examples:
            - high
        applicable_asset_types:
          anyOf:
            - items:
                type: string
              type: array
            - type: 'null'
          title: Applicable Asset Types
          description: Asset types this violation applies to
          examples:
            - - table
              - column
        is_active:
          type: boolean
          title: Is Active
          description: Whether this definition is active
          examples:
            - true
      type: object
      required:
        - id
        - name
        - fqn
        - dimension
        - default_severity
        - is_active
      title: ViolationDefinitionResponse
      description: Response model for a violation definition.
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
    ErrorInfo:
      properties:
        code:
          type: string
          title: Code
          description: >-
            Error code identifier (e.g., 'WORKFLOW_NOT_FOUND',
            'VALIDATION_ERROR')
          examples:
            - WORKFLOW_NOT_FOUND
        message:
          type: string
          title: Message
          description: Human-readable error message
          examples:
            - >-
              Workflow configuration with id
              '123e4567-e89b-12d3-a456-426614174000' not found
        details:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Details
          description: >-
            Additional error details as a dictionary (flexible structure for
            business logic errors)
          examples:
            - workflow_id: 123e4567-e89b-12d3-a456-426614174000
      type: object
      required:
        - code
        - message
      title: ErrorInfo
      description: >-
        Nested error information object.


        Note: This model uses an untyped dict for `details` to match the
        flexible error

        structure used throughout the service layer (see WorkflowServiceError
        and similar).

        This is distinct from ErrorDetail, which is used for structured
        validation errors.
    DimensionRef:
      properties:
        id:
          type: string
          format: uuid
          title: Id
          description: Unique dimension identifier
          examples:
            - 550e8400-e29b-41d4-a716-446655440011
        name:
          type: string
          title: Name
          description: Dimension name
          examples:
            - accuracy
        display_name:
          anyOf:
            - type: string
            - type: 'null'
          title: Display Name
          description: Human-readable name
          examples:
            - Accuracy
        assessment_type:
          type: string
          title: Assessment Type
          description: 'Type of assessment: ''metadata'' or ''data_quality'''
          examples:
            - data_quality
      type: object
      required:
        - id
        - name
        - assessment_type
      title: DimensionRef
      description: Lightweight reference to a dimension (for violation responses only).
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT Bearer token authentication. Include the token in the Authorization
        header as: `Authorization: Bearer <token>`. The JWT must contain valid
        client_id, and project_id claims for tenant isolation and SDK routing.

````