Associate connections with pipeline - Precisely Data Integrity Suite

Data Integrity Suite APIs
Product
Data_Integrity
Spatial_Analytics
Data_Enrichment
geo_addressing_1
Services
Spatial Analytics
Data Enrichment
Geo Addressing
ft:title
Data Integrity Suite APIs
ft:locale
en-US
PublicationType
pt_developer
copyrightfirst
2023
copyrightlast
2026

Associates source and target connections with an existing continuous pipeline.

HTML

POST https://hostname/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections

Process Overview

  1. Pipeline Verification—Validates pipeline exists and belongs to the specified project
  2. Connection Validation—Validates source and target connections
  3. Connection Association—Links the connections and applies connection parameters

Required Permissions

replication-pipeline::manage

Request

Path parameters

Key Required Type Description
projectId Yes string

The unique identifier of the project containing the pipeline
pipelineId Yes string

The unique identifier of the pipeline to configure

Request body properties

Property Required Type Description
sourceConnectionId Yes string
  • Minimum length: 1 characters
targetConnectionId Yes string
  • Minimum length: 1 characters

Request body example

"sourceConnectionId":"conn-src-uuid",
"targetConnectionId":"conn-tgt-uuid"

Response

Response examples

Example status code responses for this method are shown here.

Examples
"type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.1",
"title": "Bad Request",
"status": "400",
"detail": "Validation error occurred",
"instance": "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections",
"properties": {
  "errorCode": "DI-ADAPTER-VAL-0000"
}
 

"type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.2",
"title": "Unauthorized",
"status": "401",
"detail": "Authorization failed - missing or invalid credentials",
"instance": "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections",
"properties": {
  "errorCode": "DI-ADAPTER-AUT-0001"
}
 

"type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.4",
"title": "Forbidden",
"status": "403",
"detail": "Authorization failed - insufficient permissions",
"instance": "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections",
"properties": {
  "errorCode": "DI-ADAPTER-AUT-0002"
}
 
"type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.5",
"title": "Not Found",
"status": "404",
"detail": "Pipeline not found",
"instance": "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections",
"properties": {
  "errorCode": "DI-ADAPTER-DFL-0007"
}
 
"type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.21",
"title": "Unprocessable Entity",
"status": "422",
"detail": "Pipeline is not associated with the specified project",
"instance": "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections",
"properties": {
  "errorCode": "DI-ADAPTER-DFL-0003"
}
 

"type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.6",
"title": "Internal Server Error",
"status": "500",
"detail": "An unexpected error occurred",
"instance": "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/connections",
"properties": {
  "errorCode": "DI-ADAPTER-DFL-0006"
}