Every captured request appears in the traffic list. Filter, search, pin, and inspect — then export to cURL, HAR, or directly to a Postman collection with environments for team sharing.
Each row is a single HTTP transaction. The columns include:
App / client — which app or process made the request.
Method — GET, POST, PUT, DELETE, etc.
URL / path — the full request URL.
Status — HTTP status code and text (e.g. 200 OK, 401 Unauthorized).
Size — response body size.
Duration — total request time.
Click any row to open the detail pane with full request and response tabs: headers, body, raw, and a one-click Copy as cURL.
Performance note: The live list uses a compact format for speed. The detail pane always loads the full stored entry — complete headers and body — when you select a row.
Pinned hosts
Pinning lets you focus on the APIs you care about without scrolling past background noise.
Right-click any row and choose Pin this host to add it to your pins.
Switch between All traffic and Pinned views from the sidebar.
Pinned patterns persist across sessions — you only set them up once.
Pin by hostname, subdomain pattern, or URL prefix.
Filters & search
Use the toolbar to narrow what you see:
All — every captured transaction.
REST API — filters to JSON/API calls only.
GraphQL — shows only GraphQL queries and mutations.
Errors — 4xx and 5xx responses only.
Incomplete — requests that didn't receive a response (timeouts, cancelled).
Search — type any keyword to filter by URL, host, status, or body content.
Copy URL & Copy cURL
Right-click any row to copy the request in the format you need:
Copy URL — the bare request URL.
Copy as cURL — the full request including method, all headers, auth tokens, cookies, and body as a runnable curl command.
Sensitive data: cURL exports include Authorization headers, session cookies, and API keys exactly as captured. Treat them like passwords — do not paste into public channels or commit to version control.
Repeat requests
Select any captured row and choose Repeat to re-fire the request through the proxy. The repeated request appears as a new row in the traffic list, so you can compare the original and repeated responses side by side.
HAR export, import & replay
HAR (HTTP Archive) files make traffic reproducible and shareable:
Export HAR — save all or selected traffic to a .har file to share with teammates.
Export HAR (redacted) — strips sensitive headers (auth tokens, cookies) before exporting. Safe for sharing with external parties.
Import HAR — load a .har file to inspect traffic from another session or device.
Compare HAR files — diff two captures to spot regressions between app versions or environments.
Replay HAR — re-fire a full batch of requests to validate a bug fix or confirm consistent behaviour.
Export Postman collection — with environments
ProxyHawk advantage: Other proxy tools that offer Postman export give you a flat list of requests. ProxyHawk automatically generates environment variables — base URLs, auth tokens, and custom values — so your team can import and start testing without manually rebuilding anything.
To export captured traffic as a Postman collection:
In the traffic list, select the requests you want to include. You can select multiple rows.
Right-click and choose Export → Postman Collection.
ProxyHawk generates a .json collection file. What's included automatically:
Base URLs as {{baseUrl}} — each unique host becomes an environment variable, so switching between staging and production is a one-field change.
Auth tokens as {{authToken}} — Authorization headers are extracted into variables, not hard-coded.
All headers and body — exactly as captured from real app traffic.
Request name and grouping — requests are grouped by host for easy navigation in Postman.
In Postman, go to File → Import, select the .json file, and the collection and environment are ready to run.
This workflow captures real production traffic, structures it for your team, and eliminates the manual recreation of endpoints that slows everyone down.
