PDC API Reference
The Pentaho Data Catalog (PDC) API exposes a set of RESTful endpoints that allow you to interact programmatically with your catalog. The reference is organized into logical groups so you can quickly find the endpoints you need. Each endpoint page includes details about request methods, parameters, request/response schemas, error codes, and code examples.
How to use this reference
This API Reference is designed to help you explore and use the PDC API effectively. Each endpoint page provides the information you need to build, test, and integrate requests into your workflows.
Navigation: Endpoints are organized into logical groups (such as Health, Auth, Search, and Data Sources) so you can quickly locate the functionality you need. Use the sidebar to browse by domain.
Schemas: Every endpoint includes request and response schemas, with clear field descriptions, data types, and example payloads. This helps you understand exactly what to send and what to expect back.
Error codes: Standard error responses are listed for each endpoint. These include sample error objects with status codes, messages, and possible causes.
Code examples: Ready-to-use code snippets are provided in multiple languages. All endpoints include a
curlexample, and some also provide JavaScript, Python, or Java examples for quick integration.Authorization: All endpoints (except the
Healthcheck) require a valid bearer token in theAuthorizationheader. Refer to the Authentication page to learn how to obtain and use tokens.
Endpoint groups
The following groups of endpoints are available:
Authenticate with username and password to obtain a bearer token for secure API access.
Get, update, or filter entities and fetch profiling information for metadata analysis.
Create, retrieve, and manage data source connections across databases, files, and cloud stores.
Retrieve or create notifications to track system events, data changes, or catalog activity.
Conventions
All PDC API endpoints follow these conventions:
Base path: All endpoints are hosted under:
Authentication: Except for the Health endpoint, all requests require a bearer token. Add the token to your request headers:
Request/response format: JSON
Errors: Consistent error objects are returned across endpoints.
Last updated
Was this helpful?

