# Pynt Command CLI Mode

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

* **Pynt Command Mode**: Run automated API security tests alongside your CLI-based functional tests, integrating security seamlessly into your workflow.
  {% endhint %}

The Pynt command is a mode within the Pynt CLI that enables you to run API security tests seamlessly alongside any CLI-based functional tests. It integrates directly into your existing testing workflow without requiring changes to your test scripts.

To use the Pynt command, simply wrap your existing functional test command with pynt. This allows Pynt to intercept and analyze API traffic generated by your tests in real time, automatically identifying potential security issues.

## Basic usage

```bash
pynt command --cmd <your command line>
```

## Optional arguments

{% code overflow="wrap" fullWidth="true" %}

```bash
    --cmd - The command that runs the functional tests
    --captured-domains - Pynt will scan only these domains and subdomains. For all domains write "*"
    --test-name - A name for your Pynt scan
    --port - Set the port pynt will listen to (DEFAULT: random)
    --allow-errors - If present will allow command to fail and continue execution
    --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
    --self-signed - Use when the functional test verify SSL
    --no-proxy-export - Pynt will not export the proxy settings to the environment
    --application-id - Attach the scan to an application, you can find the ID in your applications area at app.pynt.io
    --application-name - Attach the scan to an application, application will be created automatically if it does not exist.
    --host-ca - Path to the CA file in PEM format to enable SSL certificate verification for pynt when running through a VPN.
    --severity-level - 'all', 'medium', 'high', 'critical', 'none' (default) 
    --tag - Tag the scan. Repeat for multiple tags
    --verbose - Use to get more detailed information about the run
```

{% endcode %}

## Examples

* [Pynt with pytest](/documentation/security-testing-integrations/pynt-with-testing-frameworks/pynt-for-pytest.md)
* [Pynt with Rest Assured](/documentation/security-testing-integrations/pynt-with-testing-frameworks/pynt-for-rest-assured.md)
* [Pynt with Jest](/documentation/security-testing-integrations/pynt-with-testing-frameworks/pynt-for-jest.md)
* [Pynt with curl](/documentation/security-testing-integrations/advanced-pynt-examples/pynt-with-curl.md)
* [Pynt with ReadyAPI testrunner](/documentation/security-testing-integrations/pynt-with-api-testing-clis/pynt-for-testrunner-readyapi-cli.md)

#### How Pynt command works

<figure><img src="/files/EXbaNvNbvvWK7VG0MqOz" alt=""><figcaption><p>Pynt command architecture</p></figcaption></figure>

***

{% 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-command-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.