The API Client is an HTTP request workspace built into ProxyHawk: compose requests, replay captured traffic, and export collections to Postman — all without leaving the app.
Create tabs for separate requests; use Collections to save and reopen drafts.
Compose JSON, form, or raw bodies; enable/disable header rows with checkboxes.
Send executes the request. On macOS, sends may run via the system curl binary so TLS behavior matches CLI tools and system trust stores.
Use Import to paste a cURL command and instantly populate the request tab.
Open captured requests in the API Client
From any captured row in the traffic list, open the request directly in the API Client. Headers, query parameters, and body are pre-filled. Edit what you need and hit Send — no copy-pasting required.
Export to Postman — with environments
ProxyHawk advantage: Most proxy tools stop at HAR export, leaving you to manually recreate requests in Postman. ProxyHawk exports a proper Postman collection with environment variables, so your team can import and start testing immediately.
To export captured requests as a Postman collection:
In the traffic list, select the requests you want to include (or open them in the API Client first).
Choose Export → Postman Collection from the menu.
ProxyHawk generates a .json collection file with:
Environment variables — base URLs are extracted and turned into {{baseUrl}} variables so you can switch between staging and production.
Auth tokens — Authorization headers become environment variables (e.g. {{authToken}}) rather than hard-coded strings.
All headers and body — exactly as captured from real app traffic.
In Postman, use File → Import and select the exported .json file. The collection and environment are ready to run.
This workflow means you capture real API behavior from a running app, then hand off production-accurate requests to QA or teammates — without manually reconstructing anything.
Build reusable collections from real traffic
A practical team workflow: capture first, then curate. Record live app traffic, open important rows in the API Client, and save them into named collections. This gives your team realistic regression requests built from actual production behavior — no guessing at payloads or headers.
Collections persist across sessions and can be exported to Postman at any time as environments evolve.
API Client vs HAR replay
Use API Client when you want to edit and iterate on individual requests, or when building a collection to share.
Use HAR replay when you want to re-run a larger traffic sequence quickly without editing individual requests.
Use Postman export when you want to hand off captured requests to teammates or set up environment-aware test suites.
Limitations
See Known limitations for body size caps, timeout behavior, and differences vs browser DevTools.
