Update an existing destination connector’s configuration.
The config object contains connector-specific configuration properties using dot notation. Use GET /destinations/connectors?connector_code=<type> to discover available properties — only those with user_defined: true should be included in your request.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Whether to include secret values in the response
Display name for the destination connector.
Connector type identifier (e.g., snowflake, bigquery, clickhouse, postgresql, s3).
Connector-specific configuration properties using dot notation. Use GET /destinations/connectors with connector_code to retrieve the full schema — only include properties where user_defined: true.
Successful Response
Destination connector configuration and status.
User-defined connector name
Connector type (e.g., 'snowflake', 'bigquery', 'clickhouse')
Unique identifier
Human-readable connector type name
Creation timestamp (ISO 8601)
Subscription identifier
Tenant identifier for multi-tenancy
Connector configuration parameters
List of associated topic identifiers
Mapping of topics to their partitions or related entities
List of topic names
List of task identifiers
Current status: Active, Paused, Stopped, Broken, Starting, Unassigned, Unknown, Pending
Desired state: Pending, Active, Paused, Stopped
Status information for each connector task