Proxy Traffic

APXY captures all HTTP and HTTPS traffic passing through the proxy with full request and response details.

How it works

When you run apxy start, APXY acts as a man-in-the-middle proxy:

1. HTTP traffic is intercepted and logged automatically
2. HTTPS traffic can be inspected when SSL interception is enabled for that domain
3. All captured traffic is stored in a SQLite database for querying

Web UI

In the Capture group, the Traffic view (http://localhost:8082) shows live traffic as it flows through the proxy:

• Live streaming — traffic appears in real time via Server-Sent Events (SSE)
• Density toggle — switch between comfortable and compact views for high-volume capture
• Protocol tabs — filter by All, HTTP, HTTPS, WebSocket, or JSON
• Click any row to see full request/response details, headers, body, timing, and TLS info
• Filter panel — pin filters, save presets, and search by URL/host/method

Use the Setup group to confirm readiness before you begin capturing, and use Analyze views when you want higher-level summaries of the session.

CLI

Startup flags (--ssl-domains, --bypass-domains, --mitm-all, --upstream-proxy, --project-dir, --no-system-proxy, --network-service, Web UI port, and more), plus apxy stop, apxy status, and apxy env, are all covered in CLI Reference → Proxy.

Quick example:

apxy start
# … use the app; press Ctrl+C or run `apxy stop` from another terminal
apxy stop

On macOS, apxy start can configure the system HTTP/HTTPS proxy automatically; on Linux you typically use eval $(apxy env) or manual http_proxy / https_proxy — see the Proxy reference for details.

Sessions

Traffic is organized into sessions. Each proxy startup creates a new session. Imported HAR files create a har_import session. Sessions make it easy to isolate and filter traffic from different debugging runs.

For terminal-first inspection, continue to Logs and Request & Response Viewer.