---
title: "Trigger start/stop actions for pipelines"
method: POST
path: "/v1/integration/continuous/monitoring/projects/{projectId}/pipelines/trigger"
tags: ["Monitor and Trigger Continuous Integration Projects"]
---

# Trigger start/stop actions for pipelines

`POST /v1/integration/continuous/monitoring/projects/{projectId}/pipelines/trigger`

## Request

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

Submits an asynchronous lifecycle action (START or STOP) for one or more continuous replication pipelines in a project. A 202 Accepted
response indicates the request was validated and dispatched (not that execution is complete). The response body contains a status field
(SUBMITTED or FAILED) and the Location header points to the alerts endpoint for monitoring.

Process Overview:
- Validate caller has `replication-pipeline::operate` permission.
- Interpret request: (a) pipelines omitted/empty => target all pipelines in latest deployed snapshot; (b) pipelines provided => forward as-is.
- If targeting all, fetch latest deployed snapshot and ensure at least one pipeline is available; fail otherwise.
- If action = START, optionally treat resumeRequest=true as warm/resume start; if STOP, ignore resumeRequest.
- Dispatch start or stop request through the portal client.
- Build 202 response with body status (SUBMITTED if dispatch succeeded, FAILED if an internal exception occurred) and Location header to alerts.

Key Features:
- Bulk or targeted pipeline control (omit list for ALL, supply list for specific pipelines).
- Warm/resume semantics for START via resumeRequest flag.
- Uniform 202 response; body-level status differentiates dispatch success vs failure.
- Immediate monitoring path via Location header (/projects/{projectId}/alerts) for a successfully submitted request.
- Idempotent friendly: client can safely retry on FAILED since execution had not been confirmed.

**Required Permissions:** `replication-pipeline::operate`

## Path parameters

- `projectId` string, required

## Request body

- TriggerContinuousPipelinesRequest: Request to trigger lifecycle actions (start / stop) for one or more continuous replication pipelines within a project.
  - `pipelines` string[]: List of pipeline names on which the action should be applied. If this is not provided, the action will be applied to all pipelines associated with the project.
  - `resumeRequest` boolean: Indicates whether this trigger is to resume a previously paused or failed request (idempotent retry).
  - `action` 'START' | 'STOP', required: Action to perform on the specified pipelines.

## Response `202`

Accepted. Body status field indicates SUBMITTED or FAILED; If the request is properly submitted, Location header points to alerts endpoint.

- TriggerOperationResponse: Acknowledgement response indicating the submitted trigger request for specified operation was accepted.
  - `message` string: Informational message describing the outcome of the submission.
  - `status` 'Submitted' | 'InProgress' | 'Completed' | 'Partial' | 'Failed' | 'Cancelled': Overall submission status of the trigger request.

## Other responses

- `400`: Invalid request payload
- `401`: Unauthorized - Authentication required
- `403`: Forbidden - User lacks 'replication-pipeline::operate' permission
- `404`: Project or pipelines not found
- `500`: Internal Server Error - Failed to submit trigger request

---

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