Create a new project - 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

Creates a new continuous data integration project with the specified name and parameters.

HTML

POST https://hostname/v1/integration/continuous/projects

Process Overview

  1. Validation—Verifies project name format and checks for existing project.
  2. Project Creation—Creates new project with REPLICATION type
  3. Response—Returns project ID with HTTP 201 status and Location header

Project Name Constraints

  • Must contain only letters, numbers, periods, underscores, and hyphens
  • Must not be blank
  • Must be unique (ProjectAlreadyExistsException thrown if exists)

Description

  • Optional description can be provided for project context
  • Description will be associated with the created project

Required Permissions

replication-pipeline::manage

Request

Header keys

Key Required Type Description
Location No string

URI of the newly created project.

Example: /v1/integration/continuous/projects/project-789

Request body properties

Property Required Type Description
name Yes string
  • Minimum length: 1 characters
  • Pattern: ^[a-zA-Z0-9._-]+$
description No string  

Request body example

"name":"customer-data-integration-project",
"description":"Project for managing continuous customer data integration pipelines"

Response

Header keys

Key Required Type Description
Location No string

URI of the newly created project.

Example: /v1/integration/continuous/projects/project-789

Response body properties

Property Required Type Description
id No string  

Response examples

Example status code responses for this method are shown here.

Examples
"id":"customer-data-integration-project-789"
 
"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",
"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",
"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",
"properties": {
  "errorCode":"DI-ADAPTER-AUT-0002"
}
 
"type":"https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.9",
"title":"Conflict",
"status":"409",
"detail":"Project with name 'existing-project' already exists",
"instance":"/v1/integration/continuous/projects",
"properties": {
  "errorCode":"DI-ADAPTER-PRJ-0006"
}
 
"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",
"properties": {
  "errorCode":"DI-ADAPTER-PRJ-0003"
}