---
title: "Push mainframe files"
method: POST
path: "/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/push"
tags: ["Build and Configure Mainframe Integration Projects"]
---

# Push mainframe files

`POST /v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/push`

## Request

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

Executes orchestrated push for Mainframe pipeline files.

**Features:**
- Phase-based orchestration: preflight, upload, rename, delete, reconcile
- Preflight drift detection against expected snapshot fingerprint
- Batch upload support with conflict resolution (`REPLACE_ALL`, `PARTIAL`, `FAIL`)
- Returns per-phase status, counts, and final refreshed snapshot

**Use Cases:**
- Sync local extension edits to remote mainframe pipeline assets
- Apply selective updates/deletes after local diff planning
- Guard against stale push via drift checks before write operations

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

## Path parameters

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

## Query parameters

- `includeHidden` boolean

## Response `200`

Push orchestration executed (success/partial/failure encoded in payload status)

- MainframePushResponse: Response payload for orchestrated mainframe push execution.
  - `status` 'success' | 'partial_failure' | 'failed': Overall push result status.
  - `phaseResults` PhaseResult[]: Per-phase execution summary.
    - `success` boolean: Indicates whether the phase was successful.
    - `errors` string[]: List of errors encountered during the phase if any.
  - `batchIndex` integer: Batch index acknowledged by the adapter.
  - `totalBatches` integer: Total batches for this push run.
  - `completedBatches` integer: Count of successfully applied batches.
  - `errorMessage` string: Top-level error message when push is failed or partially failed.

## Other responses

- `400`: Bad Request - Invalid request body or missing multipart payload
- `401`: Unauthorized - Authentication required
- `403`: Forbidden - Missing required permission
- `404`: Not Found - Project or pipeline does not exist
- `500`: Internal Server Error - Push orchestration execution failure

---

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