---
title: "Activate a project of any type"
method: POST
path: "/v1/integration/projects/{projectId}/activate"
tags: ["Unified Project Lifecycle APIs"]
---

# Activate a project of any type

`POST /v1/integration/projects/{projectId}/activate`

## Request

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

Activates a project through one common lifecycle contract. The `projectType` query
parameter selects the internal implementation; the request and response shapes do not change.

**Features:**
- Supports `validate`, `commit`, `deploy`, and `start` for every project type.
- Accepts common pipeline IDs and commit/deploy options.
- Ignores fields that do not apply to the selected project type.
- Preserves existing Continuous and Mainframe validation/commit orchestration.
- Uses unified Portal operations for deploy and start.
- Returns one phase-based acknowledgement envelope with a common status URL.

**Use Cases:**
- Run the existing Continuous or Mainframe activation workflow without selecting a
  type-specific public endpoint.

**Authorization:** Requires either `replication-pipeline::create` or
`replication-pipeline::update` when permission harmonization is enabled; otherwise,
`replication-pipeline::manage`.

## Path parameters

- `projectId` string, required

## Query parameters

- `projectType` 'REPLICATION' | 'MAINFRAME_REPLICATION' | 'ADVANCED_REPLICATION', required: Supported project types for unified project operations

## Request body

- UnifiedProjectActivationRequest: Common activation request for every project type. Options that do not apply to the selected project type are ignored.
  - `validate` boolean: Run project or pipeline validation before commit.
  - `commit` boolean: Commit or stage the current configuration.
  - `deploy` boolean: Deploy the committed configuration.
  - `start` boolean: Start pipelines after deployment.
  - `pipelineIds` string[]: Optional pipelines targeted by validation and Mainframe lifecycle phases.
  - `options` UnifiedActivationOptions: Common activation options shared by all project types.
    - `commitMode` 'INCREMENTAL' | 'FULL': Commit mode where supported.
    - `forceDeploy` boolean: Force deployment where supported.
    - `queueTimeoutInMinutes` integer: Queue timeout in minutes where supported.
    - `stopRequestTimeoutInMinutes` integer: Stop-request timeout in minutes where supported.
    - `tableCaptureTimeoutInMinutes` integer: Table-capture timeout in minutes where supported.

## Response `202`

Activation request accepted

- UnifiedProjectActivationResponse: Common activation acknowledgement for every project type.
  - `projectId` string: Unique project identifier.
  - `projectType` 'REPLICATION' | 'MAINFRAME_REPLICATION' | 'ADVANCED_REPLICATION': Resolved project type.
  - `status` 'ACCEPTED' | 'COMPLETED' | 'FAILED': Overall activation execution status.
  - `phases` UnifiedActivationPhases
    - `validate` UnifiedActivationPhaseResult
      - `status` 'NOT_REQUESTED' | 'IGNORED' | 'ACCEPTED' | 'PENDING' | 'SUCCEEDED' | 'FAILED'
      - `errors` string[]
    - `commit` UnifiedActivationPhaseResult
      - `status` 'NOT_REQUESTED' | 'IGNORED' | 'ACCEPTED' | 'PENDING' | 'SUCCEEDED' | 'FAILED'
      - `errors` string[]
    - `deploy` UnifiedActivationPhaseResult
      - `status` 'NOT_REQUESTED' | 'IGNORED' | 'ACCEPTED' | 'PENDING' | 'SUCCEEDED' | 'FAILED'
      - `errors` string[]
    - `start` UnifiedActivationPhaseResult
      - `status` 'NOT_REQUESTED' | 'IGNORED' | 'ACCEPTED' | 'PENDING' | 'SUCCEEDED' | 'FAILED'
      - `errors` string[]
  - `statusUrl` string: Relative URL used to poll asynchronous project status.

## Other responses

- `400`: Invalid activation request
- `401`: Unauthorized
- `403`: Forbidden — requires replication-pipeline::create or replication-pipeline::update when permission harmonization is enabled, or legacy replication-pipeline::manage otherwise
- `404`: Project not found
- `409`: Activation conflict
- `500`: Connect Portal activation failed

---

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