Update an existing source connector’s configuration.
The config object contains connector-specific configuration properties using dot notation. Use GET /sources/connectors?connector_code=<type> to discover available properties — only those with user_defined: true should be included in your request.
To add a new table to a source, update the table.include.list property to include both the existing and new tables. The value is replaced, not appended — you must send the complete list.
Example: If your source currently replicates public.orders and public.customers, and you want to add public.new_table:
{
"name": "My PostgreSQL Source",
"connector": "postgresql",
"config": {
"table.include.list": "public.orders,public.customers,public.new_table"
}
}
Important: Any tables removed from
table.include.listwill stop being replicated.
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 source connector.
Connector type identifier (e.g., postgresql, mysql, mongodb, dynamodb, sqlserveraws).
Connector-specific configuration properties using dot notation. Use GET /sources/connectors with connector_code to retrieve the full schema — only include properties where user_defined: true.
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