# Pynt Listen CLI Mode

{% hint style="success" %}
🚀 **At a Glance**:

* **Pynt Listen Mode**: Capture real-time API traffic through a proxy for in-depth security analysis, perfect for tools that generate network requests.
  {% endhint %}

**Pynt Listen** is an interactive feature in Pynt that acts as a listening proxy on a chosen port. It's designed to capture network traffic when users redirect it to this port. Pynt stays in listening mode, waiting for the user's cue. A scan on the captured traffic starts when the user presses enter, moving Pynt from waiting to actively analyzing the traffic.

Pynt can be integrated with nearly any tool that generates API traffic, provided the tool can direct its traffic through Pynt's proxy.

## Basic usage

```bash
pynt listen --captured-domains <domains to scan>
```

## Required arguments

{% code overflow="wrap" %}

```
--captured-domains - Pynt will scan only these domains and subdomains. For all domains write "*"
```

{% endcode %}

Specifying a captured domain is crucial when using `pynt listen`, particularly for web applications. Web browsers often generate a vast amount of unrelated traffic, which can clutter the scan results. By focusing on a specific domain, `pynt listen` can more effectively monitor relevant network activity.

## Optional arguments

{% code overflow="wrap" %}

```bash
    --port - Set the port pynt will listen to (DEFAULT: 5001)
    --ca-path - The path to the CA file in PEM format
    --proxy-port - Set the port proxied traffic should be routed to (DEFAULT: 6666)
    --report - If present will save the generated report in this path.
    --insecure - use when target uses self signed certificates
    --host-ca - path to the CA file in PEM format to enable SSL certificate verification for pynt when running through a VPN.
    --return-error - 'all-findings' (warnings, or errors), 'errors-only', 'never' (default),
```

{% endcode %}

**Examples**

* [Pynt with browsers](/documentation/security-testing-integrations/pynt-with-browsers.md)
* [Pynt with Burp suite](https://docs.pynt.io/documentation/api-security-testing/pynt-cli-modes/pages/doVs4aTeXMxywcY5yjCG#id-2.-use-pynt-listen-as-an-upstream-proxy-of-burp)
* [Pynt with ReadyAPI](/documentation/security-testing-integrations/pynt-with-api-testing-tools/pynt-for-readyapi.md)
* [Pynt with Insomnia](/documentation/security-testing-integrations/pynt-with-api-testing-tools/pynt-for-insomnia.md)

***

{% hint style="info" %}
For additional support, visit [Pynt Community Support](https://www.pynt.io/community).
{% endhint %}


---

# 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.pynt.io/documentation/api-security-testing/pynt-cli-modes/pynt-listen-cli-mode.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.