---
title: "Get status of target dataset creation"
method: GET
path: "/v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/datasets/status"
tags: ["Build and Configure Continuous Integration Projects"]
---

# Get status of target dataset creation

`GET /v1/integration/continuous/projects/{projectId}/pipelines/{pipelineId}/datasets/status`

## Request

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

Fetches the status of an asynchronous target dataset creation task for the specified pipeline.

Behavior & semantics:
  - The endpoint returns a `DatasetCreationStatusResponse` describing the overall
    creation status and per-schema details (total, success, in-progress, failed)
    and any per-table errors.

Status interpretation:
  - `status` (overall): one of `SUCCESS`, `PENDING`, `IN_PROGRESS`, `FAILED`.
    - SUCCESS: all tables for the requested schemas were created successfully.
    - IN_PROGRESS / PENDING: creation is still ongoing for one or more schemas.
    - FAILED: creation failed for all requested tables/schemas.
  - `schemaDetails`: per-target schema breakdown including counts and a list of
    per-table errors (if any). Use these details to diagnose failures.

Usage & polling guidance:
  - Poll the endpoint returned in the POST response `Location` header, or call
    this endpoint directly to monitor progress. Use exponential backoff when
    polling frequently to avoid overwhelming the backend service.
  - Once the overall `status` becomes `SUCCESS` or `FAILED`, the creation is
    considered terminal.

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

## Path parameters

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

## Response `200`

Successfully retrieved dataset creation status

- DatasetCreationStatusResponse: Response indicating the status of dataset creation.
  - `status` 'SUCCESS' | 'PENDING' | 'IN_PROGRESS' | 'FAILED': Overall status of the dataset creation process.
  - `schemaDetails` SchemaDetails[]: Details of the target schema where tables are being created. for type TABLE.
    - `schemaName` string: Name of the target schema where tables are created.
    - `status` 'SUCCESS' | 'PENDING' | 'IN_PROGRESS' | 'FAILED': Status of the dataset creation process.
    - `totalCount` integer: Total number of tables to be created.
    - `successCount` integer: Number of tables successfully created.
    - `inProgressCount` integer: Number of tables currently in progress of being created.
    - `failedCount` integer: Number of tables that failed to be created.
    - `errors` TableCreationError[]: List of error messages if any tables failed to be created.
      - `tableName` string: Name of the table that failed to be created.
      - `message` string: Error message associated with the table creation failure.

## Other responses

- `400`: Bad Request - Validation failed due to one of the following reasons: - Invalid query parameters (e.g., missing or invalid 'type' parameter)
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks the required 'replication-pipeline::view' or legacy 'replication-pipeline::manage' permission
- `404`: Not Found - No dataset creation status found for the given pipeline
- `422`: Unprocessable Entity - Request parameters are syntactically correct but semantically invalid: - Type parameter is not one of the allowed values [TABLE]
- `500`: Internal Server Error - Failed to retrieve status.

---

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