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

# Trigger start/stop actions for mainframe pipelines

`POST /v1/integration/mainframe/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/mainframe/monitoring/projects/{projectId}/pipelines/trigger`
- Auth: HTTP bearer

Submits an asynchronous lifecycle action (START or STOP) for one or more mainframe 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). Use the /logs and /status API to monitor the pipeline execution logs.

Process Overview:
- Validate that all specified pipeline IDs belong to the given project.
- Dispatch the start/stop action asynchronously.
- Build 202 response with body status (SUBMITTED if dispatch succeeded, FAILED if an internal exception occurred).

Key Features:
- Targeted pipeline control (supply specific pipeline IDs).
- Uniform 202 response; body-level status differentiates dispatch success vs failure.
- Monitor pipeline execution using the /logs and /status API.

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

## Path parameters

- `projectId` string, required

## Request body

- TriggerMainframePipelinesRequest: Request to trigger lifecycle actions (start / stop) for one or more mainframe pipelines within a project.
  - `pipelines` string[], required: List of pipeline IDs on which the action should be applied.
  - `action` 'START' | 'STOP', required: Action to perform on the specified pipelines.

## Response `202`

Accepted - Trigger request submitted successfully

- 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
- `406`: Not Acceptable. The trigger request was validated but failed to dispatch.
- `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)