API client
The API client (⌘2) is a request composer built into elcapture. Write a request by hand, or send one straight from the traffic list with Edit & send, change it, and fire it — the response lands back in the traffic list so every tool applies to it.
Compose a request
Each request is a tab. Set the method and URL, add headers, and pick a body:
- Body: None, JSON, Form, Text or Multipart.
- Auth: None, Bearer, Basic, API key or Digest.
Organise saved requests into collections, keep values in environments, and reuse cookies and history across sends.
Impersonate a client
Send as a real client's TLS and header fingerprint: Chrome, Firefox, Safari, Safari iOS or OkHttp. Useful when a server behaves differently for a browser than for a bare HTTP library.
Send options
| Option | Does |
|---|---|
| Follow redirects | Follow 3xx responses automatically. |
| Timeout | Give up after N milliseconds (default 30000). |
| Count & concurrency | Send the request many times, several at once. |
| Delay | Wait between sends. |
| Direct | Skip your rules for this send. |
By default sends route through the proxy, so they appear in the traffic list with everything else.
Code snippets
Turn any request into client code (More → Code snippet, or the row menu) in 13 forms: cURL, HTTPie, Python requests, JavaScript fetch, Node axios, Go net/http, Swift URLSession, Kotlin OkHttp, Rust reqwest, PHP Guzzle, Raw HTTP, URL and Markdown.