> ## 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.

# Generic export by key

> Dispatches to the per-key export handler that matches `key`. Use this endpoint for keys that
don't have a dedicated path on this page (e.g. `reporting_tickets`, `reporting_messages`,
`reporting_worklog`, `survey`). The accepted query parameters and response shape depend on
the chosen key — see the dedicated schema blocks (`exportReportingTickets`,
`exportReportingMessages`, `exportReportingWorklog`, `exportSurveyResponses`) in
`endpoints/export.yaml` for the per-key contract.

Large result sets are queued asynchronously and delivered to the current user's email; small
sets stream the file in the response body.




## OpenAPI

````yaml https://dev.enneo.dev/api/mind/docs/open-api get /export/{key}
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:
  /export/{key}:
    get:
      tags:
        - Export
      summary: Generic export by key
      description: >
        Dispatches to the per-key export handler that matches `key`. Use this
        endpoint for keys that

        don't have a dedicated path on this page (e.g. `reporting_tickets`,
        `reporting_messages`,

        `reporting_worklog`, `survey`). The accepted query parameters and
        response shape depend on

        the chosen key — see the dedicated schema blocks
        (`exportReportingTickets`,

        `exportReportingMessages`, `exportReportingWorklog`,
        `exportSurveyResponses`) in

        `endpoints/export.yaml` for the per-key contract.


        Large result sets are queued asynchronously and delivered to the current
        user's email; small

        sets stream the file in the response body.
      operationId: genericExport
      parameters:
        - name: key
          in: path
          required: true
          description: Export key — identifies the dataset and column projection to export.
          schema:
            type: string
          example: reporting_tickets
        - name: format
          in: query
          required: false
          description: >-
            Export format. Defaults to the backend `defaultDateExportFormat`
            setting.
          schema:
            type: string
            enum:
              - xlsx
              - csv
              - json
          example: json
      responses:
        '200':
          description: Successful operation — file body or async-confirmation payload.
          content:
            application/json:
              schema:
                type: object
            application/octet-stream:
              schema:
                type: string
                format: binary
        '400':
          description: Unknown or invalid export key.
        '403':
          description: Unauthorized.
        '500':
          description: Internal error.
components:
  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

````