History
ApiWorkbench remembers the last 100 requests you sent. Use History to get back to a request you did not save, or to repeat something you sent earlier.
Open History
Select History on the rail. On a phone, open the drawer with the menu button and select the History icon at the top.
The newest request is at the top. Each row shows:
| Part | Example | Meaning |
|---|---|---|
| Method | GET | The HTTP method. DELETE is shortened to DEL. |
| URL | {{baseUrl}}/orders/42 | The address as you typed it, with variables not filled in |
| Status | 200 | The status code, coloured by its class. A request that failed before any status arrived shows Error. |
| Time | 85 ms | How long the response took |
| Age | 2 min ago | When you sent it: just now, minutes, hours (h) or days (d) ago |
Point at the status line for an explanation of that status code.
Before you send anything, the panel reads No requests yet.
Reopen a request
Click a row. A copy of the request opens in a new tab, exactly as it was when you sent it: method, URL, params, headers, body, auth, tests and settings.
- The tab is a draft. It is not linked to a collection, even if the original request was. Select Save… to keep it. See Save a request.
- Because the copy is not in a collection, it does not see collection variables and cannot inherit auth from a collection. If it relied on those, open the saved request from Collections instead.
- The response is not restored. Select Send to get a new one.
Search history
Type in Search history at the top of the panel. The list narrows to requests whose URL contains the text. Upper and lower case do not matter.
Search matches the URL as written, so orders finds {{baseUrl}}/orders/42, but searching for the server name does not find a request that uses {{baseUrl}}.
Clear history
Select the sweep icon, Clear all history, at the top of the panel.
WARNING
The list is cleared at once, without asking, and cannot be brought back. Single entries cannot be removed.
What is recorded
| Recorded | Not recorded |
|---|---|
| The request as sent from the editor with Send | Response bodies and headers |
| The status code, the duration and the time | Requests sent by the runner or a load test |
| WebSocket, Socket.IO, MQTT, Server-Sent Events and gRPC sessions | |
| Saved examples of the request |
When the list reaches 100 entries, the oldest ones drop off.
To see everything that went over the wire, including redirects and requests made by scripts, use the Console.
Privacy
History is a file in the app's data folder on your device. It holds each request in full, including any tokens or passwords typed straight into its fields. It is not encrypted and is not sent anywhere.
If you share a computer, use {{variables}} for secrets so they are not written into history, and clear history when you are done. See Files and data.
History or a collection?
| Use History when | Use a collection when |
|---|---|
| You want to repeat something from a few minutes ago | You will need the request again next week |
| You forgot to save a request | You want names, folders, variables and shared auth |
| You are exploring an API | You want to run, test or export a set of requests |
History is short-term memory. Save anything you care about in a collection.