---
title: "Delete a pipeline by ID"
method: DELETE
path: "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}"
tags: ["Build and Configure Continuous Integration Projects"]
---

# Delete a pipeline by ID

`DELETE /v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}`

## 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}`
- Auth: HTTP bearer

Deletes a pipeline by its ID within a project with comprehensive cleanup options. This operation can be performed
synchronously or asynchronously depending on the cleanup operations required.

**Process Overview:**
- **Validation Phase**: Validates project and pipeline existence, association, and user permissions
- **Pipeline State Check**: Determines if pipeline is currently running
- **Graceful Shutdown** (if pipeline is running):
  - Stops the pipeline execution
  - Disables data capture (if `disableCapture` is true)
  - Clears pending backlog (if `clearBacklog` is true)
  - Stops associated log reader processes (if `stopLogReader` is true)
- **Configuration Cleanup**: Removes pipeline configuration and associated resources

**Execution Modes:**
- **Synchronous**: For simple pipeline deletions (stopping and deleting without cleanup operations)
- **Asynchronous**: For complex deletions requiring extensive cleanup operations (e.g., disabling capture, clearing backlog, stopping log readers)

**Pre-deletion Operations:**
- **Disable Capture**: Stops data replication while preserving existing data
- **Clear Backlog**: Removes pending data changes that haven't been processed
- **Stop Log Reader**: Gracefully shuts down log reading processes

**Key Considerations:**
- Running pipelines are automatically stopped before deletion
- Monitor deletion progress using the endpoint returned in the `Location` header for 202 responses

**Required Permissions:** `replication-pipeline::delete` when permission harmonization is enabled; otherwise, `replication-pipeline::manage`.

## Path parameters

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

## Request body

- DeletePipelineRequest: Request payload for deleting a pipeline. This includes flags for optional pre-requisite operations.
  - `disableCapture` boolean: Flag to indicate whether to disable data capture for the pipeline
  - `clearBacklog` boolean: Flag to indicate whether to clear any pending backlog for the pipeline
  - `stopLogReader` boolean: Flag to indicate whether to stop log reader processes associated with the pipeline

## Response `202`

Pipeline deletion initiated successfully. Use the Location header to monitor progress.

## Other responses

- `204`: Pipeline deleted successfully.
- `400`: Invalid request payload.
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks the required 'replication-pipeline::delete' or legacy 'replication-pipeline::manage' permission
- `404`: Pipeline not found.
- `500`: Internal Server Error - Unexpected server error during deletion.

---

[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)