The request you need again is the one you just sent
Debugging an API is repetitive by nature: send, adjust one thing, send again. History means the second send is a click rather than a rebuild.
Find the call in the sidebar
Every call made from the API Client is listed in the sidebar with the most recent at the top. It is a chronological record of what you actually did, which is often more useful than what you meant to do.
Load it back and edit it
Click any entry and the request loads into the editor with its original method, URL, headers and body. Edit whatever you are iterating on and send again.
Keep responses across refreshes
Responses from the current session are cached, so you can revisit one without re-sending. By default that cache is session-only โ refresh and it clears.
History lives on your machine and is not synced to the cloud. When a request is worth keeping, save it into a collection.






