> For the complete documentation index, see [llms.txt](https://metalbear.com/mirrord/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metalbear.com/mirrord/docs/using-mirrord/connecting-tools/postman.md).

# Postman

Connect Postman to your cluster via mirrord.

By routing Postman traffic through a local SOCKS5 proxy, you can send API requests to kubernetes internal services (e.g., `http://my-service:8080`) directly from your local machine.

### Prerequisites

This guide assumes you have already set up a local proxy using `microsocks` and `mirrord`. If you haven't done this yet, please follow the [setup guide](/mirrord/docs/using-mirrord/connecting-tools.md) first to launch the proxy.

### Configuration

1. Ensure the prerequisite [SOCKS5 proxy](/mirrord/docs/using-mirrord/connecting-tools.md) is running with `mirrord` and targeting the desired cluster.
2. Open Postman and open Settings (click the gear icon in the top right > **Settings**).
3. Select the **Proxy** tab.
4. Under **Proxy configurations for sending requests**:
   * Toggle **Use custom proxy configuration** to **ON**.
   * Enable **HTTP** and **HTTPS**.
   * Select **socks5h** as the proxy server protocol.
   * Enter `127.0.0.1` as the proxy server hostname.
   * Enter `1080` as the proxy server post (or the port you configured).
5. Ensure **Proxy Auth** is **OFF**.
6. Close the settings window.

### Verify

You can now use cluster DNS names in your requests.

* Create a new request.
* Enter an internal URL (e.g., `http://my-service.namespace.svc.cluster.local:8080`).
* Click **Send**.


---

# 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://metalbear.com/mirrord/docs/using-mirrord/connecting-tools/postman.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.