> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-1.11/network-and-node-management/networking.md).

# Networking

This page describes how network communication works in Catalyst for participants, domains, and applications. Components running inside the cluster communicate using Kubernetes internal DNS names, while selected services and APIs can also be exposed externally through ingress routes.

### Participants

For every participant running on Catalyst, the following (internal) endpoints are available:

| Endpoint                     | Address                                                                |
| ---------------------------- | ---------------------------------------------------------------------- |
| **Ledger API**               | `<canton-participant-name>.<namespace>.svc.cluster.local:5011`         |
| **Admin API**                | `<canton-participant-name>.<namespace>.svc.cluster.local:5019`         |
| **HTTP JSON API (internal)** | `jsonapi-<canton-participant-name>.<namespace>.svc.cluster.local:7011` |
| **HTTP JSON API (external)** | `http(s)://<canton-participant-name>.<your-domain>`                    |

{% hint style="info" %}
Default ports are shown above. If you set custom ports when creating a participant, the values will differ.
{% endhint %}

### Domains

For every domain running on Catalyst, the following (internal) endpoints are available:

| Endpoint                 | Address                                                   |
| ------------------------ | --------------------------------------------------------- |
| **Public API**           | `<canton-domain-name>.<namespace>.svc.cluster.local:5018` |
| **Admin API**            | `<canton-domain-name>.<namespace>.svc.cluster.local:5019` |
| **Ingress (if enabled)** | `http(s)://<canton-domain-name>.<your-domain>`            |

{% hint style="info" %}
Default ports are shown above. If you set custom ports when creating a domain, the values will differ.
{% endhint %}

### Applications

For every application running on Catalyst, the following endpoints are available:

| Type             | Address                                                      |
| ---------------- | ------------------------------------------------------------ |
| **Internal**     | `<application-name>.<namespace>.svc.cluster.local:80`        |
| **Backend app**  | `http(s)://<subdomain>.<your-domain>/<application-name>/api` |
| **Frontend app** | `http(s)://<subdomain>.<your-domain>/<application-name>`     |

{% hint style="info" %}
The default port (80) is used above. If you set a custom port when creating an application, the value will differ.
{% endhint %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-1.11/network-and-node-management/networking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.