> ## Documentation Index
> Fetch the complete documentation index at: https://microstrate-1133-notifications-prefs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Submit contact form

> Submits a contact form
- The function provides a structured mechanism for authenticated users to send inquiries, feedback, or support requests directly to the quiva.ai team or specific team members. This communication channel is integrated within the platform, allowing users to reach out for assistance without leaving the application environment.



## OpenAPI

````yaml /api-reference/endpoint/accounts/openapi.json post /accounts/submit-contact-form
openapi: 3.0.3
info:
  title: quiva.ai Gateway
  description: >-
    API for managing accounts, users, authentication, and payments in the
    quiva.ai platform
  version: 1.0.0
  contact:
    name: quiva.ai Support
    url: https://app.quiva.ai
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Account Management
    description: Operations related to account creation, updating, and deletion
  - name: User Management
    description: Operations related to user creation, updating, and deletion
  - name: Authentication
    description: Operations related to authentication and session management
  - name: API Keys
    description: Operations related to API key management
  - name: Multi-Factor Authentication
    description: Operations related to MFA setup and verification
  - name: Payment
    description: Operations related to subscription and payment management
  - name: Mesh Nodes
    description: Operations related to mesh node management
paths:
  /accounts/submit-contact-form:
    post:
      tags:
        - Account Management
      summary: Submit contact form
      description: >-
        Submits a contact form

        - The function provides a structured mechanism for authenticated users
        to send inquiries, feedback, or support requests directly to the
        quiva.ai team or specific team members. This communication channel is
        integrated within the platform, allowing users to reach out for
        assistance without leaving the application environment.
      operationId: submitContactForm
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ContactRequest'
            example:
              to_email: support@example.com
              subject: Billing question
              location: Account settings
              message: I have a question about my billing cycle.
              phone_number: '+1234567890'
              preferred_contact_method: email
      responses:
        '200':
          description: Contact form submitted successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    ContactRequest:
      type: object
      properties:
        to_email:
          type: string
          format: email
          description: Recipient email
        subject:
          type: string
          description: Email subject
        location:
          type: string
          description: Location in the application
        message:
          type: string
          description: Message content
        phone_number:
          type: string
          description: Phone number
        preferred_contact_method:
          type: string
          description: Preferred contact method
          enum:
            - emai
            - phone
      required:
        - to_email
        - subject
        - message
    SuccessResponse:
      type: object
      properties:
        message:
          type: string
    Error:
      type: object
      properties:
        error:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-Api-Key

````