# Create Pipeline

```
POST /api/v1/create_pipeline
```

## **Request Body (JSON):**

```json
{
  "virtual_cluster_id": "vci_xxx",
  "pipeline_name": "my-pipeline"
}
```

### **CURL Example:**

```bash
curl https://api.warpstream.com/api/v1/create_pipeline \
-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{"virtual_cluster_id": "vci_xxx", "pipeline_name": "my-pipeline"}'
```

## **Response Body (JSON):**

```json
{
  "pipeline_id": "pipeline-xyz",
  "pipeline_name": "my-pipeline",
  "pipeline_state": "paused",
  "pipeline_type": "bento",
  "pipeline_deployed_configuration_id": "" // Initially empty
}
```

## Create Orbit Pipeline

You can also use the `create_pipeline` api to create an Orbit pipeline. Simply add a `pipeline_type` of `orbit` to the request above.

```
POST /api/v1/create_pipeline
```

### **Request Body (JSON):**

```json
{
  "virtual_cluster_id": "vci_xxx",
  "pipeline_name": "my-pipeline",
  "pipeline_type": "orbit"
}
```

### **Response Body (JSON):**

```json
{
  "pipeline_id": "pipeline-xyz",
  "pipeline_name": "my-pipeline",
  "pipeline_state": "paused",
  "pipeline_type": "orbit",
  "pipeline_deployed_configuration_id": "" // Initially empty
}
```

### **CURL Example:**

<pre><code><strong>curl https://api.warpstream.com/api/v1/create_pipeline \
</strong>-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{"virtual_cluster_id": "vci_xxx", "pipeline_name": "my-pipeline", "pipeline_type": "orbit"}'
</code></pre>

**Note that you can only have a single Orbit pipeline at a time.** To create a new Orbit pipeline first [delete](/warpstream/reference/api-reference/pipelines/delete-pipeline.md) the old one.

## Create Schema Linking Pipeline

You can also use the `create_pipeline` api to create a Schema Linking pipeline. Simply add a `pipeline_type` of `schema_linking` to the request above.

```
POST /api/v1/create_pipeline
```

### **Request Body (JSON):**

```json
{
  "virtual_cluster_id": "vci_sr_xxx",
  "pipeline_name": "my-pipeline",
  "pipeline_type": "schema_linking"
}
```

### **Response Body (JSON):**

```json
{
  "pipeline_id": "pipeline-xyz",
  "pipeline_name": "my-pipeline",
  "pipeline_state": "paused",
  "pipeline_type": "schema_linking",
  "pipeline_deployed_configuration_id": "" // Initially empty
}
```

### **CURL Example:**

<pre><code><strong>curl https://api.prod.us-east-1.warpstream.com/api/v1/create_pipeline \
</strong>-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{"virtual_cluster_id": "vci_sr_xxx", "pipeline_name": "my-pipeline", "pipeline_type": "schema_linking"}'
</code></pre>

**Note that you can only have a single Schema Linking pipeline at a time for each schema registry cluster.** To create a new Schema Linking pipeline first [delete](/warpstream/reference/api-reference/pipelines/delete-pipeline.md) the old one.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.warpstream.com/warpstream/reference/api-reference/pipelines/create-pipeline.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.