Get metabases for a connection - 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

Retrieves metabase configuration associated with a specific data connection inside a project.

HTML

GET https://hostname/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/metabases

A metabase is the replication metadata repository used by Precisely Replication / Connect CDC to store:

  • Subscription and capture metadata
  • Replication state
  • Internal bookkeeping required to run CDC pipelines reliably

In most deployments there is 0 or 1 metabase per connection per project. This endpoint is modeled as a list for consistency with project-level responses and future extensibility.

Typical usage

  • UI/agent workflow to show whether a connection already has a metabase configured
  • Validation step before creating / updating pipeline components

Required Permissions

replication-pipeline::view

Request

Path parameters

Key Required Type Description
projectId Yes string

Project identifier
connectionId Yes string

Connection identifier

Response

For a successful response, the method returns 200 with an array. If no metabase is associated with the given connection, the method returns 200 with an empty array. If the project does not exist or it is not accessible, the method returns 404.

Response body properties

Property Required Type Description
name No string  
version No string  
dataConnectionId No string  
vaultConnectionId No string  
parameters No object  

Response examples

Example status code responses for this method are shown here.

Examples
{
  "name": "BQDEV2111",
   "version": "40n",
   "dataConnectionId": "conn-src-uuid",
  "vaultConnectionId": "vault-connection-uuid",
  "parameters": {
    "IN_SYSBAS": "true"
   }
}
 
"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}/connections/{connectionId}/metabases",
"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}/connections/{connectionId}/metabases",
"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}/connections/{connectionId}/metabases",
"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}/connections/{connectionId}/metabases",
"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}/connections/{connectionId}/metabases",
"properties": {
  "errorCode": "DI-ADAPTER-MBS-0003"
}