Update an existing source connector.
The config object contains connector-specific properties using dot notation
(e.g., table.include.list, schema.include.list, database.hostname).
To add tables, include the full table.include.list value with the new tables appended.
Use the GET /sources/connectors endpoint with a connector_code query parameter to
retrieve the full configuration schema for a specific connector type.
Documentation Index
Fetch the complete documentation index at: https://docs.streamkap.com/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Whether to include secret values in the response
When False, save config and return immediately without waiting for KC update
Request body for updating an existing source connector.
Display name for the source connector.
Connector type identifier (e.g., 'postgresql', 'mysql', 'mongodb', 'dynamodb', 'sqlserveraws').
Configuration properties for the AlloyDB source connector.
KC cluster to deploy this connector to. Omit for default cluster.
List of tag IDs to assign to this source
Successful Response
Source connector configuration and status.
User-defined connector name
Connector type (e.g., 'postgresql', 'mysql', 'mongodb')
Unique identifier
Human-readable connector type name
Creation timestamp (ISO 8601)
Subscription identifier
Tenant identifier for multi-tenancy
Associated service identifier
Configuration properties for the AlloyDB source connector.
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
KC cluster this connector is deployed to. None means default cluster.
Status information for each connector task
List of tag IDs assigned to this source