Create a new source connector.
The config object contains connector-specific properties using dot notation
(e.g., table.include.list, schema.include.list, database.hostname).
Use the GET /sources/connectors endpoint with a connector_code query parameter to
retrieve the full configuration schema for a specific connector type.
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 deployment
Request body for creating a new source connector.
Display name for the source connector.
Connector type identifier (e.g., 'postgresql', 'mysql', 'mongodb', 'dynamodb', 'sqlserveraws').
Connector-specific configuration properties using dot notation (e.g., 'table.include.list', 'schema.include.list'). Use the GET /sources/connectors endpoint with a connector_code query parameter to retrieve the full configuration schema for a specific connector type.
Origin of the entity creation.
terraform, web, api Desired operational state of the source.
Pending, Active, Paused, Stopped, Pending Update, Pending Delete 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
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