# Postman

Postman supports per-collection / per-request proxies for both gateway and ISP products. Recommended for testing username variants quickly.

## Global proxy

1. **Settings → Proxy → Use custom proxy configuration**.
2. Server: `gate.helodata.io`, Port: `7777` (or your ISP IP).
3. **Proxy Auth → on**. Username + password.
4. Toggle **Proxy** in the top-right action area.

\[screenshot: Postman Proxy settings tab]

This affects every request in the workspace.

## Per-environment

Create environments named `helo-us`, `helo-de`, etc. Each holds the proxy username variant:

| Variable     | Value                                 |
| ------------ | ------------------------------------- |
| `proxy_user` | `helo_s1a2b3c4d5e-type-res-region-us` |
| `proxy_pass` | sub-user password                     |

Then in **Settings → Proxy** reference them: `{{proxy_user}}`, `{{proxy_pass}}`. Switching the environment switches geo.

## Pre-request script (dynamic session)

Mint a fresh session ID per request:

```js
const sid = Math.random().toString(36).slice(2, 10);
pm.environment.set("proxy_user",
  `helo_s1a2b3c4d5e-type-res-region-us-session-${sid}-sesstime-10`
);
```

## Postman collection (provided)

helodata publishes an official collection covering:

* All REST API endpoints (sub-users, orders, traffic, whitelists, …)
* One sample request per product type with the right username structure

Import URL:

```
https://api.helodata.com/v1/postman/collection.json
```

See [Postman collection](/api-reference/postman.md) for details.

## Verify

Add a request to `https://ipv4.icanhazip.com`. Send — the body should show a helodata exit IP.

## Common pitfalls

* **Postman desktop vs web** — only the desktop app honors the proxy setting; the web client tunnels through Postman's own servers.
* **Newman (CLI runner)** uses the same settings file. For CI runs, pass `--global-proxy` or set `HTTPS_PROXY` envvar before `newman run`.
* **Self-signed certs at the target** — Postman validates upstream certs. helodata doesn't re-issue, so a target self-signed cert still fails; toggle **SSL certificate verification** off if needed.


---

# Agent Instructions: 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.helodata.com/integrations/ai-and-workflow/postman.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.