---
title: "Import mainframe pipelines from ZIP"
method: POST
path: "/v1/integration/mainframe/projects/{projectId}/import"
tags: ["Build and Configure Mainframe Integration Projects"]
---

# Import mainframe pipelines from ZIP

`POST /v1/integration/mainframe/projects/{projectId}/import`

## Request

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

Imports multiple mainframe pipelines from a ZIP archive containing their configurations and associated files.

**Process Overview:**
1. **Request Validation** - Validates ZIP file
2. **Archive Extraction** - Extracts pipeline configurations and files from ZIP
3. **Pipeline Creation** - Creates pipelines based on extracted configurations
4. **File Association** - Associates extracted files with created pipelines
5. **Validation** - Validates imported pipeline configurations

**Key Features:**
- Bulk import support for multiple pipelines in a single operation
- Supports pipeline configurations, parameters, and associated files
- Validates imported configurations before creation

**Use Cases:**
- Restore pipeline configurations from backup
- Transfer pipeline configurations between environments
- Deploy pre-configured pipeline sets

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

## Path parameters

- `projectId` string, required

## Response `201`

Pipelines successfully imported from ZIP archive

- MainframePipelineImportResponse: Response containing the results of importing mainframe pipelines from a ZIP archive
  - `successes` MainframeImportPipelineSuccess[]: List of pipelines that were successfully imported
    - `projectId` string: Unique identifier of the project where the pipeline was imported
    - `pipelineId` string: Unique identifier assigned to the imported pipeline
    - `pipelineName` string: Original name of the pipeline in the ZIP archive
    - `importedPipelineName` string: Name of the pipeline after import (may differ if renamed due to conflicts)
    - `status` 'IMPORTED' | 'IGNORED': Import status of the pipeline
  - `errors` MainframeImportPipelineError[]: List of pipelines that failed to import with error details
    - `errorType` 'PIPELINE_ERROR' | 'RUNTIME_ENGINE_ERROR' | 'CONFLICT_ERROR': Type of error that occurred during import: - CONFLICT_ERROR: A pipeline with the same name already exists, use conflict resolutions in import request.
    - `pipelineName` string: Name of the pipeline that failed to import
    - `errorMessage` string: Detailed error message explaining what went wrong

## Other responses

- `400`: Bad Request - Validation failed due to one of the following reasons: - Invalid project ID - Invalid archive format - Invalid file size
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks the required 'replication-pipeline::create' or legacy 'replication-pipeline::manage' permission
- `404`: Not Found - Resource not found due to one of the following reasons: - Project does not exist
- `500`: Internal Server Error - Server encountered an unexpected condition, such as: - Pipeline import operation failure - ZIP archive extraction failure - Pipeline creation failure during import

---

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