> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/troubleshooting/connectivity-guides/consume-internal-api-pipelines-ztna.md).

# How to consume Internal API pipelines using ZTNA

Learn how to consume and publish pipelines configured as Internal API in realms using ZTNA.

On the Digibee Integration Platform, [**ZTNA (Zero Trust Network Access)**](/documentation/connectivity-management/ztna.md) is an extra layer of security that can be applied in pipelines, ensuring that services are securely and privately accessed.

For realms using ZTNA, the process for consuming internal APIs is similar to realms using VPN. Supported triggers for this feature include: [**HTTP**](/documentation/connectors-and-triggers/triggers/web-protocols/http.md), [**HTTP File**](/documentation/connectors-and-triggers/triggers/web-protocols/http-file.md), and [**REST**](/documentation/connectors-and-triggers/triggers/web-protocols/rest.md).

## **Enabling Internal API**

To enable the Internal API feature in your realm:

1. Contact [Digibee Support](/documentation/troubleshooting/help-and-faq/support.md).
2. Provide your **Edge Router** details for registration.
   * The IP or DNS of the Edge Router you have configured in your infrastructure.
   * The port to send traffic to.

This information allows Digibee to create the inverse flow connecting your network to Digibee’s, ensuring secure and private communication. Inverse Flow in the Digibee Integration Platform allows you to execute calls from your infrastructure to internal pipelines within the Platform using ZTNA.

## **Configuring a pipeline to use Internal API**

To configure the pipeline using the Internal API:

1. Choose a supported trigger: [**HTTP**](/documentation/connectors-and-triggers/triggers/web-protocols/http.md), [**HTTP File**](/documentation/connectors-and-triggers/triggers/web-protocols/http-file.md), and [**REST**](/documentation/connectors-and-triggers/triggers/web-protocols/rest.md).
2. Enable **Internal API** and **API Key** in the trigger configuration form.
3. Assign the pipeline to an [API Key](/documentation/platform-administration/settings/api-keys-consumers.md).
4. [Deploy the pipeline](/documentation/development-cycle/overview/deployment/deployments.md) on the **Run** page.
5. Open the card of the deployed pipeline to find the access link in this format: `​`

   `https://{replace-with-Digibee-internal-host}/pipeline/realm/v1/{{pipeline-name}}`

## **Consuming pipelines through ZTNA**

To consume a pipeline using ZTNA:

1. Use the **IP address of the Edge Router** and the environment-specific ZTNA mapping port:

* **Production environment:** Use port **7070**: `http://{{IP-EDGE}}:7070/pipeline/realm/v1/{{pipeline-name}}`
* **Test environment:** Use port **9090**: `http://{{IP-EDGE}}:9090/pipeline/realm/v1/{{pipeline-name}}`

{% hint style="warning" %}
Use HTTP instead of HTTPS when calling the pipeline. ​
{% endhint %}

For additional details, refer to the documentation on [ZTNA implementation on the Digibee Integration Platform](/documentation/connectivity-management/ztna.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/troubleshooting/connectivity-guides/consume-internal-api-pipelines-ztna.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.