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

# Validate a value of the given type

> Validates a value against the rules of the specified validation type. Supported types are `email` and `letterAddress`.



## OpenAPI

````yaml https://dev.enneo.dev/api/mind/docs/open-api post /validation/{type}
openapi: 3.0.0
info:
  version: '1'
  title: enneo.MIND API
  description: This describes the API of enneo Mind, the main ticketing backend
  contact:
    name: enneo GmbH
    email: richard@enneo.ai
  license:
    name: Proprietary software
    url: https://enneo.ai
servers:
  - url: https://demo.enneo.ai/api/mind
    description: Production server, demo client
  - url: https://main.enneo.dev/api/mind
    description: Development main branch
  - url: http://localhost:8005/api/mind
    description: Local development server
security:
  - bearerAuth:
      - api
  - cookieAuth:
      - api
paths:
  /validation/{type}:
    post:
      tags:
        - General
      summary: Validate a value of the given type
      description: >-
        Validates a value against the rules of the specified validation type.
        Supported types are `email` and `letterAddress`.
      operationId: validate
      parameters:
        - name: type
          in: path
          required: true
          description: The validation type to apply.
          schema:
            type: string
            enum:
              - email
              - letterAddress
          example: email
      requestBody:
        description: The value to validate
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - value
              properties:
                value:
                  type: string
                  description: >
                    The value to validate. For `email`, an email address. For
                    `letterAddress`, a postal address

                    (name + street + zip/city), separated by newlines or commas.
                  example: user@example.com
      responses:
        '200':
          description: Validation result
          content:
            application/json:
              schema:
                type: object
                properties:
                  valid:
                    type: boolean
                    description: Whether the value is valid
                    example: true
                  reason:
                    type: string
                    description: >-
                      The reason why the value is invalid (only present if valid
                      is false)
                    example: Invalid email address format
        '400':
          description: Bad request — missing required field or unsupported type
          content:
            application/json:
              schema:
                type: object
                properties:
                  valid:
                    type: boolean
                    example: false
                  reason:
                    type: string
                    example: >-
                      Invalid validation type. Supported types: email,
                      letterAddress
        '500':
          description: Internal error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      description: Data format of Enneo error messages
      properties:
        error:
          type: string
          example: Contract 121 could not be processed
          description: Readable error message that should be shown to the user
        details:
          type: string
          example: >-
            Uncatched null point exception in testFunction() in
            /app/src/file:212
          description: Not easily readable error message that is for the developer
        txId:
          type: string
          example: c916167c94
          description: >-
            Internal transaction id. Useful for debugging. Corresponds to the
            OpenTelemetry trace ID.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT-based authentication
      x-scopes:
        api: Full access to the API
    cookieAuth:
      type: apiKey
      in: cookie
      name: connect.sid
      description: Cookie-based authentication
      x-scopes:
        api: Full access to the API

````