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

# List connector types

> List every connector type and the exact ``config`` and ``secrets`` keys it accepts.

Read this before creating a connection. Each field carries its API ``key``
(what you send), the ``label`` the UI and validation errors use for it (so a
rejection naming "Database" maps back to ``pg_db``), whether it is
``required``, and an ``example`` where one helps. ``applies_when`` marks
fields that only apply under a particular auth or mode choice.

Credentials belong in ``secrets`` and are never returned by any response;
everything listed under ``config`` is stored in the clear and readable back.

``undocumented_types`` names connector types the product supports whose keys are
not published yet. They are creatable, but only through the app — this listing
omits them rather than risk naming a key wrongly, which would send a caller down
a path that silently fails.



## OpenAPI

````yaml https://api.summation.com/openapi.json get /v1/connections/data/types
openapi: 3.1.0
info:
  title: summation-api public API
  version: 0.1.0
servers: []
security: []
tags:
  - name: Auth
    description: Machine authentication for API clients.
  - name: Tenant
    description: Organization and tenant context resolved by summation-api.
  - name: Projects
    description: Project resources.
  - name: Conversations
    description: Conversation and message resources.
  - name: Reports
    description: Report resources and report operations.
  - name: Runs
    description: Project run history and execution status.
  - name: Playbooks
    description: Playbook resources.
  - name: Files
    description: Project file resources.
  - name: Catalog Entries
    description: Project-scoped data asset attachments.
  - name: Data Connectors
    description: Reusable external data source connections.
  - name: App Connectors
    description: External app connectors whose tools the agent can use during chat.
  - name: Tables
    description: Canonical table metadata and catalog.
  - name: Views
    description: Canonical Summation view metadata and catalog.
  - name: Query Executions
    description: Read-only SQL query execution.
  - name: Grid
    description: Materialized grid status, sync, and lineage.
  - name: Schedules
    description: Schedule and schedule run inspection.
paths:
  /v1/connections/data/types:
    get:
      tags:
        - Data Connectors
      summary: List connector types
      description: >-
        List every connector type and the exact ``config`` and ``secrets`` keys
        it accepts.


        Read this before creating a connection. Each field carries its API
        ``key``

        (what you send), the ``label`` the UI and validation errors use for it
        (so a

        rejection naming "Database" maps back to ``pg_db``), whether it is

        ``required``, and an ``example`` where one helps. ``applies_when`` marks

        fields that only apply under a particular auth or mode choice.


        Credentials belong in ``secrets`` and are never returned by any
        response;

        everything listed under ``config`` is stored in the clear and readable
        back.


        ``undocumented_types`` names connector types the product supports whose
        keys are

        not published yet. They are creatable, but only through the app — this
        listing

        omits them rather than risk naming a key wrongly, which would send a
        caller down

        a path that silently fails.
      operationId: list_connector_types
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '400':
          description: Invalid request or unsupported option.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemError'
        '401':
          description: Missing, invalid, or expired credentials.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemError'
        '403':
          description: Authenticated but missing the required scope.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemError'
        '404':
          description: Resource not found or not accessible.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemError'
        '429':
          description: Rate limit exceeded.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemError'
        '500':
          description: Internal server error.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemError'
      security:
        - SummationMachineAuth:
            - agent:read
components:
  schemas:
    ProblemError:
      description: >-
        Public error envelope (RFC 7807 ``application/problem+json``).


        Mirrors the body produced by :func:`api_error`. Declaring it in the
        contract

        lets generated clients type error handling instead of guessing.
      properties:
        type:
          description: URI reference identifying the problem type.
          title: Type
          type: string
        title:
          description: Short, human-readable summary of the problem type.
          title: Title
          type: string
        status:
          description: HTTP status code.
          title: Status
          type: integer
        detail:
          description: Human-readable explanation specific to this occurrence.
          title: Detail
          type: string
        code:
          description: Stable, machine-readable error code.
          title: Code
          type: string
        request_id:
          description: Correlation id, echoed in the x-request-id header.
          title: Request Id
          type: string
      required:
        - type
        - title
        - status
        - detail
        - code
        - request_id
      title: ProblemError
      type: object
  securitySchemes:
    SummationMachineAuth:
      type: oauth2
      flows:
        clientCredentials:
          scopes:
            agent:read: agent:read
            agent:write: agent:write
          tokenUrl: /v1/auth/m2m/token

````