How the Web Proxy Works
What happens when you send an API request from Yaak in your browser
Yaak Web uses a proxy to send HTTP requests because browsers restrict direct API access. Before your first send, Yaak shows the proxy’s address and asks you to approve it.
Your browser → Proxy → Your API
What the proxy can see
Your prepared request passes through the proxy, including its URL, headers, body, and selected cookie jar. The proxy also receives the API’s response. Its operator can read this data, including credentials, so use a proxy you trust.
HTTPS encrypts each connection, but the proxy can still read the data between them. An HTTP destination leaves the proxy-to-API connection unencrypted.
Storage and logging
Your workspace and response history stay in your browser. The proxy processes requests and responses in memory without saving their bodies or retaining cookies between sends.
By default, proxy logs contain a startup message and operational warnings and errors, not request details. Detailed logging is opt-in for debugging. Hosting infrastructure may keep separate access logs.
Other options
Use the desktop app to send directly from your computer, including to local or private APIs. You can also self-host Yaak. The hosted proxy blocks private network addresses; on a self-hosted instance, localhost refers to the proxy’s machine.
Was this helpful?