Access service endpoints - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Use REST API endpoints generated from deployed quality pipelines. Submit data from external applications, workflows, or business systems to validate addresses, standardize data, geocode records, and match information without opening the pipeline designer. Use service endpoints to automate workflows with pipeline logic, integrate quality functions into portals, CRMs, onboarding systems, or ETL tools, and batch-process multiple records by API instead of manual file uploads.

Preview: This feature is currently in Preview for select workspaces and might be subject to change before general availability.

The Services tab displays all deployed pipelines as service endpoints. Use the Deployed on filter to view services deployed on Cloud or Agent. Each service generates a unique REST API endpoint that you can call from your applications.

  1. Select a deployed pipeline from the list.
  2. Go to the Services tab.
    You will see a table with these details for each service:
    • Service Name: Automatically generated from the pipeline name (for example, Pipeline_e2e_us_address_data_2).
    • HTTP Method: POST, which means the API accepts data in the request body.
    • Endpoint URL: The REST URL where you submit data (for example, /v1/api/service/{serviceName}/runconf).
  3. Review the input and output schemas before integrating the service into your application. Select Try it out to test the service endpoint.
You can now submit data to your service endpoint and receive processed results.

The Responses section shows error codes that occur if validation fails or required fields are missing, and the output schema based on the final step of the pipeline.

Submit data to a service endpoint

Each service requires a request body that matches the input schema of the pipeline's first step. The interface displays all required fields, example values, and expected data types.

Example request body:

{
  "e2e_us_address_data": [
    {
      "AddressLine2": "string",
      "AddressLine1": "string",
      "FirmName": "string",
      "StateProvince": "string",
      "InputValue": "string",
      "Postcode": "string",
      "City": "string"
    }
  ]
}
Note:
  • Field names must match those defined in the pipeline's input step.
  • You can submit multiple records in a single request.
  • All values should be sent as strings unless otherwise specified in the pipeline schema.