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

# Update connector connection

> Tenant-bound connector configuration. No provider requests. Credentials are masked. Mutations require the current revision where applicable. Referenced connections and nonempty connectors cannot be deleted. New custom connector and action creation requires workspace rollout enablement.



## OpenAPI

````yaml /openapi.json patch /connectors/{connectorId}/connections/{connectionId}
openapi: 3.0.3
info:
  title: Visito M2M API
  version: 1.0.0
  description: >-
    Tenant-scoped server-to-server API for channels, conversations, commerce,
    custom AI tools, and WhatsApp templates. Send operations are asynchronous
    and return queued acknowledgements. Expansion adds conversation controls,
    knowledge, sales opportunities, delivery status, reporting, and signed
    webhooks.
servers:
  - url: https://platform-api.visitoai.com/m2m/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Channels
  - name: Conversations
  - name: Commerce
  - name: Custom tools
  - name: WhatsApp templates
  - name: Properties
  - name: Knowledge
  - name: Sales CRM
  - name: Delivery
  - name: Reporting
  - name: Webhooks
  - name: Tickets
    description: >-
      General tickets, escalations and Commerce-backed work. See the Tickets
      developer guide for lifecycle, MCP arguments, permissions and retry
      workflows.
    externalDocs:
      description: Tickets developer guide
      url: https://docs.visitoai.com/api-docs/tickets
paths:
  /connectors/{connectorId}/connections/{connectionId}:
    patch:
      summary: Update connector connection
      description: >-
        Tenant-bound connector configuration. No provider requests. Credentials
        are masked. Mutations require the current revision where applicable.
        Referenced connections and nonempty connectors cannot be deleted. New
        custom connector and action creation requires workspace rollout
        enablement.
      operationId: update_connector_connection
      parameters:
        - name: connectorId
          in: path
          required: true
          schema:
            type: string
        - name: connectionId
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConnectorConnectionPatch'
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConnectorConnectionResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    ConnectorConnectionPatch:
      type: object
      additionalProperties: false
      properties:
        name:
          type: string
          maxLength: 120
          minLength: 1
        baseUrl:
          type: string
          maxLength: 2048
        enabled:
          type: boolean
        auth:
          $ref: '#/components/schemas/ToolAuthInput'
        revision:
          type: integer
          minimum: 0
      required:
        - revision
    ConnectorConnectionResponse:
      type: object
      properties:
        connection:
          $ref: '#/components/schemas/ConnectorConnection'
      required:
        - connection
      additionalProperties: false
    ToolAuthInput:
      type: object
      required:
        - type
      properties:
        type:
          type: string
          enum:
            - none
            - bearer
            - api_key
        headerName:
          type: string
        value:
          type: string
          writeOnly: true
      additionalProperties: false
    ConnectorConnection:
      type: object
      properties:
        connectorId:
          type: string
        tenantId:
          type: string
        connectionId:
          type: string
        integrationId:
          type: string
        name:
          type: string
        displayName:
          type: string
        accountEmail:
          type: string
          nullable: true
        propertyId:
          type: string
        baseUrl:
          type: string
        enabled:
          type: boolean
        active:
          type: boolean
        degraded:
          type: boolean
        status:
          type: string
        revision:
          type: integer
          minimum: 0
        version:
          type: integer
          minimum: 0
        createdAt:
          type: string
        updatedAt:
          type: string
        auth:
          type: object
          required:
            - type
            - configured
          properties:
            type:
              type: string
              enum:
                - none
                - bearer
                - api_key
            headerName:
              type: string
            secretLastFour:
              type: string
            configured:
              type: boolean
      additionalProperties: false
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: Visito M2M API key
      description: Server-side tenant-scoped credential created from Build > API Keys.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.