Delete a project by ID - Precisely Data Integrity Suite

Data Integrity Suite APIs
Product
Data_Integrity
Spatial_Analytics
Data_Enrichment
geo_addressing_1
Services
Spatial Analytics
Data Enrichment
Geo Addressing
ft:title
Data Integrity Suite APIs
ft:locale
en-US
PublicationType
pt_developer
copyrightfirst
2023
copyrightlast
2026

Deletes a project by its ID. Supports optional deletion of project configuration only.

HTML

DELETE https://hostname/v1/integration/continuous/projects/{projectId}

Process overview

  1. Validates that the project exists and the user has permission to delete it.
  2. If configOnly is true, deletes only the project configuration from the Data Integrity Suite.
  3. If configOnly is false (default), performs a full deletion including runtime components.

Configuration only deletion behavior

Delete project configuration only. This action is not recommended. Use this option only when the runtime engines for this project no longer exist. This action cannot be undone. Exporting the project before continuing is highly recommended.

After the project configuration is deleted from the Data Integrity Suite: Any processes that have not been stopped will continue to run. You cannot stop the project, disable capture, delete metabases, or monitor the project. Manual cleanup of runtime engine processes, metabases, and log readers will be needed.

Required permissions

replication-pipeline::manage

Request

Path parameters

Key Required Type Description
projectId Yes string

The unique identifier of the project to delete.

Query parameters

Key Required Type Description
configOnly No boolean

Set this query parameter to true to delete only the project configuration.

Response

Header keys

Key Required Type Description
Location No string

URI to monitor deletion progress.

Example: /v1/integration/continuous/projects/project-123/deletion-status

Response examples

{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.1",
  "title": "Bad Request",
  "status": 400,
  "detail": "Validation error occurred",
  "instance": "/v1/integration/continuous/projects/{projectId}",
  "properties": {
    "errorCode": "DI-ADAPTER-VAL-0000"
  }
}
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.2",
  "title": "Unauthorized",
  "status": 401,
  "detail": "Authorization failed - missing or invalid credentials",
  "instance": "/v1/integration/continuous/projects/{projectId}",
  "properties": {
    "errorCode": "DI-ADAPTER-AUT-0001"
  }
}
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.4",
  "title": "Forbidden",
  "status": 403,
  "detail": "Authorization failed - insufficient permissions",
  "instance": "/v1/integration/continuous/projects/{projectId}",
  "properties": {
    "errorCode": "DI-ADAPTER-AUT-0002"
  }
}
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.5",
  "title": "Not Found",
  "status": 404,
  "detail": "Not Found - Resource does not exist",
  "instance": "/v1/integration/continuous/projects/{projectId}",
  "properties": {
    "errorCode": "DI-ADAPTER-PRJ-0005"
  }
}
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.6",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "An unexpected error occurred",
  "instance": "/v1/integration/continuous/projects/{projectId}",
  "properties": {
    "errorCode": "DI-ADAPTER-PRJ-0006"
  }
}