View entire request response flow
Feature Request
Nice app, really like the clean and responsive GUI and (of course) local-only.
I'm alot for the low-level though, one huge improvement (IMHO) would be the possibility to have the entire request/response flow in the results-tab in plain-text, as opposed to only seeing the response. Maybe it is already possible to show the request (?) but I could not find a setting for it.
Ideally, I would have loved if it was possible to show request(headers+body), followed by response(headers+body), as plain-text similar to how 'curl -v' does it.
Keep up the good work!
Great suggestion, and this is definitely something I plan to add!
Yeah, I agree, this is really important so you can review headers, body, etc, but mainly for your dynamic variables
Adding another vote to the pile :-) I often find myself needing to share both request and response (documenting APIs, sharing examples with team-mates) in chat and tickets. I currently do this by copy/pasting the request as cURL (Yaak makes this easy, which is great), then the body and headers of the response separately. The ability to copy/paste the whole thing in consistent HTTP format would be most welcome!
I’d also love to see the Auth flow included in that. Right now i have some issues with our identity provider on OAuth2.0 flow and i cannot figure out what is wrong since there is no information about the auth request itself. In postman i can just pop up the network inspector of electron, maybe that would be good option as well here?
Absolutely something I need. I'm testing permissions based on a folder-specific token generation request, but the bearer token that's used in the requests authorization header is not visible anywhere, so problems are impossible to debug
Alright, I’m just starting this now!
For some background, the current
reqwestlibrary that Yaak uses is a black box and doesn’t allow Yaak to see what’s going on under the hood.So I’m going to try switching to
libcurlfor sending HTTP requests, which allows inspecting exactly what happens (`curl -v`). Curl will also enable other benefits, like the ability to send case-sensitive headers (no Rust HTTP clients can do this because header handling is built into the Rust std lib).If Curl ends up being the solution, the migration path for future releases will be:
(both) Enable new
libcurlbackend to see the debug view(default) Default Yaak to using
libcurlbackend(curl) Remove old backend
I would very much appreciate this as well! Also this post has helped me understand that “reqwest” was not a typo as well 😅
Glad this is in progress. It sounds like it will enable most things that are currently making me switch tools. I need the full transcripts of the exchanges. Nothing fancy required. Dumping to a file would be just fine. I would really appreciate it if it could capture the auth sessions too. If there were a post-request/post-response hook and a dump_bytes function, that’d solve all my problems because then I can see exactly what’s actaully going over the wire anywhere in the program.
Merry Christmas! Yaak will now show the request headers in the response pane.
I also want to implement:
- Show request body that was sent
- Show a log similar to
curl -v- Show redirect chain
Let me know what else you want to see.
@Greg Schier That's not good. With the switch to libcurl, it seems like it no longer reads/sets cookies, and therefore nothing works in APIs with jwt in cookie authentication.
Hey there! Yaak hasn’t switched to libcurl, but the network stack has been (almost) completely rewritten. I’ve just shipped a fix for cookies in Beta 5!
Thanks! I love yaak ❤️
https://yaak.app/changelog/2026.1.0