Skip to main content
All ClickPipes types can be created, updated, and deleted programmatically using the ClickHouse Cloud OpenAPI. This page covers authentication and the available ClickPipes endpoints, with example curl requests for each ClickPipe type.

Authentication

The ClickHouse Cloud API uses HTTP Basic authentication. You need an API key (key ID + key secret) with permissions on the target service. See Managing API keys for instructions on creating one. Set up the following environment variables before running any of the examples below:

Base URL

Endpoints

All ClickPipes endpoints are scoped to a ClickHouse Cloud service: For CDC ClickPipes (Postgres, MySQL, MongoDB), there are additional org-level endpoints for shared CDC infrastructure scaling: For the full request and response schemas for each endpoint, see the Swagger UI.

Examples

List ClickPipes

Get a ClickPipe

Stop or start a ClickPipe

Delete a ClickPipe

Creating ClickPipes

The POST /clickpipes request body varies by source type. The examples below show the structure for each supported ClickPipe type. For the authoritative JSON schemas, refer to the Swagger UI.

Kafka

Supported Kafka-compatible sources: kafka, confluent, msk, azureeventhub, redpanda, warpstream.

Amazon Kinesis

Amazon S3

Google Cloud Storage

serviceAccountKey must be the base64-encoded content of a GCP service account JSON key file.

Azure Blob Storage

Postgres CDC

MySQL CDC

MongoDB CDC

BigQuery

serviceAccountFile must be the base64-encoded content of a GCP service account JSON key file.
Last modified on July 2, 2026