---
title: "Activate a project"
method: POST
path: "/v1/integration/continuous/projects/{projectId}/activation"
tags: ["Build and Configure Continuous Integration Projects"]
---

# Activate a project

`POST /v1/integration/continuous/projects/{projectId}/activation`

## Request

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

Stages and optionally activates a project, with optional pipeline start.

**Process Overview:**
- Based on the `ProjectActivationRequest`, this endpoint triggers the appropriate operations in a fixed sequence: validate, stage, activate, then start pipelines.
- If `validate` is true, pipeline activation readiness is validated before staging or before activation. When `validateOptions.pipelineIds` is provided, those pipelines are validated first as a pipeline-level pre-check; the full project is still validated afterward regardless.
- If `stage` is true, the project configurations are staged, and the user is redirected to the staging status endpoint.
- If `activate` is true, the project is activated, and the user is redirected to the alerts endpoint.
- If `startPipelines` is true, the pipelines associated with the project are started.
- If `stage`, `activate`, and `startPipelines` are all false but `validate` is true, the same readiness pre-check runs and a full-project validation is triggered directly, without staging.

**Redirect Details:**
- When `stage` is true, the `Location` header in the response contains the URI to monitor the staging status of the project.
- When `activate` is true, the `Location` header in the response contains the URI to the project's alerts endpoint.
- Clients can use the `Location` header to navigate to the appropriate endpoint for further actions.

**Key Features:**
- Allows users to manage the lifecycle of a project (staging, activation, pipeline starting).
- Provides redirection to relevant endpoints based on the operation performed.
- Ensures that the operations are performed asynchronously where applicable.

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

## Path parameters

- `projectId` string, required

## Request body

- ProjectActivationRequest: Request payload for activating a project. This includes flags and options for staging, activation, and pipeline start operations. It supports detailed configurations such as forced operations and timeouts.
  - `validate` boolean: Flag to indicate whether pipeline activation readiness should be validated before staging is committed
  - `validateOptions` ValidateOptions: Options for validating pipeline activation readiness before staging is committed
    - `pipelineIds` string[]: IDs of specific pipelines to validate readiness for before validating the entire project. When provided, these pipelines are validated first as a pipeline-level pre-check; the full project is still validated afterward regardless. When omitted, only the project-level validation is performed.
  - `stage` boolean, required: Flag to indicate whether the project should be staged
  - `stagingOptions` StagingOptions: Options for staging the project
    - `type` 'INCREMENTAL_COMMIT' | 'FULL_COMMIT', required: Type of staging
  - `activate` boolean, required: Flag to indicate whether the project should be activated
  - `activationOptions` ActivationOptions: Options for activating the project
    - `forced` boolean: Flag to indicate whether activation should be forced, overriding any existing active configurations
    - `queueTimeoutInMinutes` integer: Queue timeout in minutes
    - `stopRequestTimeoutInMinutes` integer: Stop request timeout in minutes
    - `tableCaptureTimeoutInMinutes` integer: Table capture timeout in minutes
  - `startPipelines` boolean, required: Flag to indicate whether pipelines within the project should be started

## Response `202`

Project activation or staging initiated successfully.

## Other responses

- `400`: Invalid request payload.
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks 'replication-pipeline::create' or 'replication-pipeline::update' when permission harmonization is enabled, or legacy 'replication-pipeline::manage' otherwise.
- `422`: Unprocessable Entity - One or more pipelines pre-checks failed activation readiness validation (staging, Metabase, user database, table mapping, or dataset). Issues are grouped by pipeline ID in the `errors` property; staging is not committed.
- `500`: Internal Server Error - Unexpected server error during activation.

---

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