---
title: "Add a sink to a pipeline"
method: POST
path: "/pipeline/{pipeline_id}/sink"
tags: ["Pipeline Nodes"]
---

# Add a sink to a pipeline

`POST /pipeline/{pipeline_id}/sink`

## Path parameters

- `pipeline_id` string, uuid, required

## Request body

- object
  - `type` 'mezmo' | 'mezmo-archive' | 'http' | 'cloudwatch-logs' | 'cloudwatch-metrics' | 'sqs' | 'notification-channel' | 'azure-blob-storage' | 'kinesis-firehose' | 'kinesis-streams' | 'elasticsearch' | 'gcp-cloud-monitoring' | 'gcp-cloud-storage' | 'gcp-cloud-operations' | 'gcp-cloud-pubsub' | 'honeycomb-logs' | 'indexed-search' | 'kafka' | 'loki' | 'new-relic' | 'prometheus-remote-write' | 'pulsar' | 'redis' | 'splunk-hec-logs' | 'sumo-logic-logs' | 'sumo-logic-metrics' | 'vector' | 's3' | 'blackhole' | 'datadog-logs' | 'datadog-metrics' | 'clickhouse' | 'opentelemetry', required
  - `deploy_type` 'saas' | 'local'
  - `title` string, nullable
  - `description` string, nullable
  - `user_config` object, required
  - `inputs` string[] — A list of inputs for the given sink. Typically this is empty when creating a new sink via the UI, but is leveraged by the terraform provider when managing pipeline state.

## Response `200`

Default Response

---

[API](https://skmtc.net/mezmo/apis/pipeline-api.md) · [All operations](https://skmtc.net/mezmo/apis/pipeline-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mezmo/pipeline-api/revisions/fb2535545d90/schema)