---
title: "PUT /v2/connector-config/{id}"
method: PUT
path: "/v2/connector-config/{id}"
---

# PUT /v2/connector-config/{id}

`PUT /v2/connector-config/{id}`

## Path parameters

- `id` string, required — The id of the connector config, starts with `ccfg_`

## Request body

- object
  - `display_name` string
  - `disabled` boolean
  - `config` object, nullable

## Response `200`

Successful response

- union
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'acme-apikey', required
    - `config` object, required — Base configuration for api key connector
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'acme-oauth2', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'asana', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'bigquery', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'box', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'calendly', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'confluence', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'databricks', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'discord', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'dropbox', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'figma', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'github', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'google-calendar', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'google-docs', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'google-drive', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'google-mail', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'google-sheet', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'hubspot', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'instagram', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'jira', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'linear', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'monday', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'notion', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'onedrive', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'outlook', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'resend', required
    - `config` object, required — Base configuration for api key connector
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'salesforce', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'sendgrid', required
    - `config` object, required — Base configuration for api key connector
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'sharepoint', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'slack-deployed-agent', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'slack', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'snowflake', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'spotify', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'youtube', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'zendesk', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'zoom', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'apollo', required
    - `config` object, required
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'plaid', required
    - `config` object, required
      - `envName` 'sandbox' | 'development' | 'production', required
      - `credentials` object, nullable
        - `clientId` string, required
        - `clientSecret` string, required
      - `clientName` string, required — The name of your application, as it should be displayed in Link. Maximum length of 30 characters. If a value longer than 30 characters is provided, Link will display "This Application" instead.
      - `products` string[], required
      - `countryCodes` string[], required
      - `language` 'en' | 'fr' | 'es' | 'nl' | 'de', required
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'postgres', required
    - `config` object, required
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'slack-agent', required
    - `config` object, required
      - `challenge_response` string, required — USER_PASTED_TOKEN - SLACK_ONETIME_CHALLENGE_CODE
      - `challenge_code` string, required — Previous challenge code - e.g. challenge_slack_abc123xyz
      - `service_token` string — Service token - xoxb-...
      - `event_subscription_url` string — Initial event subscription URL
      - `app_id` string — App ID - A1234567890
      - `client_id` string — Client ID - 1234567890.1234567890
      - `client_secret` string — Client secret - abc123...
      - `verification_token` string — Verification token - xyz123...
      - `signing_secret` string — Signing secret - abc123...
      - `initial_oauth_url` string — Initial OAuth URL - https://slack.com/oauth/v2/authorize?...
      - `app_name` string — App name - Replit Agent App
      - `app_description` string — App description - Replit integration app for Slack workspace
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'slack-agent-builder', required
    - `config` object, required
      - `oauth` object, nullable — Base oauth configuration for the connector
        - `client_id` string, nullable
        - `client_secret` string, nullable
        - `scopes` string[], nullable
        - `redirect_uri` string, nullable — Custom redirect URI
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'stripe', required
    - `config` object, required
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'stripe-agent-sandbox', required
    - `config` object, required
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'twilio', required
    - `config` object, required
  - object
    - `id` string, required
    - `created_at` string, required
    - `updated_at` string, required
    - `org_id` string, required
    - `display_name` string, nullable, required
    - `disabled` boolean, nullable, required
    - `metadata` object, nullable — JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged
    - `connector_name` 'workato', required
    - `config` object, required

## Other responses

- `400` — Invalid input data
- `401` — Authorization not provided
- `403` — Insufficient access
- `404` — Not found
- `500` — Internal server error

---

[API](https://skmtc.net/openintegrations/apis/openint-api.md) · [All operations](https://skmtc.net/openintegrations/apis/openint-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openintegrations/openint-api/versions/1b84cd7f5c05/schema)