---
title: "Update pipeline parameter"
method: PUT
path: "/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/parameters/{parameterId}"
tags: ["Build and Configure Mainframe Integration Projects"]
---

# Update pipeline parameter

`PUT /v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/parameters/{parameterId}`

## 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}/parameters/{parameterId}`
- Auth: HTTP bearer

Updates an existing pipeline parameter by its unique identifier with new values, type, or description.

**Process Overview:**
1. **Request Validation** - Validates parameter payload and identifier
2. **Parameter Retrieval** - Fetches existing parameter to check current state
3. **Security Validation** - Ensures encrypted parameters cannot be changed to plain text
4. **Parameter Update** - Updates the parameter with new details

**Parameter Types:**
- `PARAMETER_DATA_TYPE_STRING` - Plain text parameter for non-sensitive values
- `PARAMETER_DATA_TYPE_ENCRYPTED_STRING` - Encrypted parameter for sensitive values like passwords

**Security Constraints:**
- Encrypted parameters cannot be changed to plain text (STRING type)
- This prevents accidental exposure of sensitive data

**Parameter Naming Rules:**
- Variable name cannot have a space or special characters except underscore (_)

**Use Cases:**
- Modify parameter values or descriptions
- Change parameter types (with security constraints)
- Update pipeline configuration parameters

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

## Path parameters

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

## Request body

- MainframePipelineParameterRequest: A single name/value pipeline parameter.
  - `name` string, required: Parameter name
  - `value` string, required: Parameter value
  - `type` 'PARAMETER_DATA_TYPE_STRING' | 'PARAMETER_DATA_TYPE_ENCRYPTED_STRING': Parameter type
  - `description` string: Optional human-friendly description for the parameter

## Response `204`

Parameter updated successfully

## Other responses

- `400`: Bad Request - Validation failed due to one of the following reasons: - Invalid project ID - Invalid pipeline ID - Invalid parameter payload (missing required fields) - Invalid parameter type (must be PARAMETER_DATA_TYPE_STRING or PARAMETER_DATA_TYPE_ENCRYPTED_STRING) - Parameter name contains spaces or special characters (except underscore) - Encrypted parameter cannot be changed to plain text
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks the required 'replication-pipeline::update' or legacy 'replication-pipeline::manage' permission
- `404`: Not Found - Resource not found due to one of the following reasons: - Pipeline does not exist within the project - Parameter does not exist within the pipeline
- `500`: Internal Server Error - Server encountered an unexpected condition, such as: - Parameter update operation 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)