---
title: "Associate source and target connections with an existing continuous pipeline"
method: POST
path: "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections"
tags: ["Build and Configure Continuous Integration Projects"]
---

# Associate source and target connections with an existing continuous pipeline

`POST /v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections`

## Request

- Base URL: `https://integration-adapter.connect.cloud.precisely.com`
- URL: `https://integration-adapter.connect.cloud.precisely.com/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections`
- Auth: HTTP bearer

Associates source and target connections with an existing continuous pipeline.

**Process Overview:**
1. **Pipeline Verification** - Validates pipeline exists and belongs to the specified project
2. **Connection Validation** - Validates source and target connections
3. **Parameter Processing** - Applies default parameters based on connection type and merges with user-provided parameters
4. **Connection Association** - Links the connections and applies final parameters to the pipeline

**Parameter Handling:**
- **Default Parameters**: Applied based on target connection type (e.g., KAFKA connections get 15 default Kafka parameters)
- **User Parameters**: Optional sourceParameters and targetParameters can be provided to override defaults
- **Parameter Validation**: Only valid parameters for the connection type are accepted
- **Unknown Parameters**: Invalid parameters are logged with warnings and ignored

**Example for KAFKA Target:**
- Default parameters include: ACKNOWLEDGMENT, MESSAGE_FORMAT, PARTITION_MESSAGES_BY, LOB_MAX_SIZE, etc.
- User can override any default parameter by providing it in targetParameters
- Only parameters valid for KAFKA connection type are accepted

**Required Permissions:** Either `replication-pipeline::create` or `replication-pipeline::update` when permission harmonization is enabled; otherwise, `replication-pipeline::manage`.

## Path parameters

- `projectId` string, required
- `pipelineId` string, required

## Request body

- ContinuousPipelineConnectionsRequest: Request payload for associating source and target connections with an existing Continuous Replication Pipeline
  - `sourceConnectionId` string, required: The ID of the source data connection to use for the pipeline. A data connection contains information on how to access the database or data source along with the required credentials.
  - `targetConnectionId` string, required: The ID of the target data connection to use for the pipeline. A data connection contains information on how to access the database or data along with the required credentials.
  - `sourceParameters` object: Optional custom source connection parameters to override defaults. Parameters should match known parameter names; unknown parameters will be ignored with a warning.
  - `targetParameters` object: Optional custom target connection parameters to override defaults. When target connection type is KAFKA, these parameters will override the default Kafka parameters. Parameters should match known parameter names; unknown parameters will be ignored with a warning. Common Kafka parameters include: ACKNOWLEDGMENT, ENABLE_TRANSACTION_BUNDLING, INCLUDE_IMAGE_OPTION, LOB_MAX_SIZE, MESSAGE_FORMAT, PARTITION_MESSAGES_BY, etc.

## Response `204`

Connections successfully associated with the pipeline

## Other responses

- `400`: Bad Request - Validation failed due to one of the following reasons: - Missing or invalid source connection ID - Missing or invalid target connection ID
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks 'replication-pipeline::create' or 'replication-pipeline::update' when permission harmonization is enabled, or legacy 'replication-pipeline::manage' otherwise
- `404`: Not Found - Requested pipeline was not found: - Pipeline not found for the given pipelineId
- `422`: Unprocessable Entity - Request is syntactically correct but semantically invalid: - Pipeline is not associated with the specified project - Resource conflicts or constraints violations
- `500`: Internal Server Error - Server encountered an unexpected condition, such as: - Pipeline retrieval failure (PipelinesRetrievalFailedException) - Connection association failure (ConnectionsAssociationWithPipelineFailedException) - Catalog asset retrieval failure (CatalogAssetRetrievalFailedException) - Connection service client errors when fetching connection details - Data Catalog service client errors when validating connections - Service unavailability - Connection service errors - Internal processing failures

---

[API](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service.md) · [All operations](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service/llms.txt) · [OpenAPI document](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service/revisions/2d2629f4987d?raw)