Skip to main content
How-to guideApplies to: Unified engine deployments
Discover existing catalogs and relations without executing a data query.

Browse a connected catalog

Choose a catalog ID from the first response. namespace is a JSON array encoded as a query value, such as [“analytics”]. Replace the placeholders in your client. Keep returned IDs for later requests. Paths below use the native API prefix; adjust it for your deployment.

1. List catalogs

Endpoint reference.

2. Read the chosen catalog

Endpoint reference.

3. List namespaces

Endpoint reference.

4. List relations

Endpoint reference. Read the first response and choose a catalog ID. Enter it under Example values. Use the actual ID, not the display name. Read its configuration and revision, then list namespaces. Set namespace to a JSON array string, such as ["analytics"], before listing relations. Empty [] means the root namespace, not every namespace. For a connection that does not exist, use the validate-catalog and create-catalog reference operations. Configuration and credential reference fields depend on the provider. Follow the catalog recipes for exact provider setup, then verify through these HTTP reads. Table inspection can return snapshots, history, files, or summaries. Use a pinned snapshot where the endpoint supports it if your investigation must refer to one table version.
Last modified on November 4, 2026