Unified Project Lifecycle APIs

Get project status

Retrieves the existing project status response. Validation and commit fields retain their current behavior. Continuous Replication projects may additionally include analyzeStatus while conversion analysis status is available; the field is omitted otherwise.

Features:

  • Returns a complete status envelope: validation phase, per-scope results, findings, severity level, completion percentage, and the most recent commit state. - Optionally returns analyzeStatus for Continuous Replication conversion analysis polling.
  • Use the Location URI returned by a 202 Accepted validation response as the polling target; continue polling while validateStatus.status is INPROGRESS.
  • Works for all project types: Continuous Replication, Mainframe, and Advanced Replication.

Use Cases:

  • Poll semantic validation progress after triggering a FULL scope validation. - Poll conversion analysis after calling analyzeProjectConversion when analyzeStatus is present, until its status reaches a terminal state.
  • Check whether a project has been committed and is ready for activation.
  • Inspect per-scope findings and severity after a completed validation.

Authorization: Requires replication-pipeline::view.

get/v1/integration/projects/{projectId}/status

Request

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

Path parameters

projectIdstring required

Unique identifier of the project

Response

Status retrieved

projectIdstring

Unique identifier of the project

Example response

{
  "validateStatus": {
    "status": "COMPLETED",
    "lastUpdatedOn": "2026-08-12T06:22:07Z",
    "message": "DSL validation completed: DSL_ONLY=PASSED",
    "completePercentage": 100,
    "projectValidation": {
      "severityLevel": "VALID",
      "message": "PASSED | DSL_ONLY=PASSED",
      "scopeStatuses": [
        {
          "scope": "DSL_ONLY",
          "status": "PASSED",
          "message": "DSL_ONLY validation passed",
          "findings": [
            {
              "findingId": "disdsl-E-008",
              "category": "PIPELINE",
              "severity": "ERROR",
              "layer": "SEMANTIC",
              "dslPath": "pipelines[0].name",
              "message": "Duplicate pipeline name detected",
              "errorCode": "disdsl-E-008",
              "line": 14,
              "column": 3,
              "sourceFile": "pipelines/customer.dis.yaml"
            }
          ]
        }
      ]
    }
  },
  "commitStatus": {
    "status": "COMPLETED",
    "lastUpdatedOn": "2026-08-12T06:22:07Z",
    "projectValidation": {
      "severityLevel": "VALID",
      "message": "PASSED | DSL_ONLY=PASSED",
      "scopeStatuses": [
        {
          "scope": "DSL_ONLY",
          "status": "PASSED",
          "message": "DSL_ONLY validation passed",
          "findings": [
            {
              "findingId": "disdsl-E-008",
              "category": "PIPELINE",
              "severity": "ERROR",
              "layer": "SEMANTIC",
              "dslPath": "pipelines[0].name",
              "message": "Duplicate pipeline name detected",
              "errorCode": "disdsl-E-008",
              "line": 14,
              "column": 3,
              "sourceFile": "pipelines/customer.dis.yaml"
            }
          ]
        }
      ]
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.