> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Browse a catalog

> Discover existing catalogs and relations without executing a data query.

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"].

| Placeholder | Value |
| - | - |
| `{{catalog_id}}` | Your environment value. |
| `{{namespace}}` | `"[]"` |

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

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/catalogs?limit=10
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/list-catalogs.md).

#### 2. Read the chosen catalog

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/catalogs/{{catalog_id}}
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/get-catalog.md).

#### 3. List namespaces

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/catalogs/{{catalog_id}}/namespaces
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/list-namespaces.md).

#### 4. List relations

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/catalogs/{{catalog_id}}/relations?namespace=tpcds&limit=10
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/list-relations.md).

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](https://docs.e6data.com/transformation/recipes/overview.md) 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.