Skip to main content

Features ›Collections, Favorites & History

Collections, Favorites & History

Collections

A collection is a named group of saved requests, like Users API or Payments - staging.

Create a collection

Click the New Collection (+) button in the Collections title bar and type a name.

A Templates collection is always there, listed first, for requests you reuse as starting points. It can't be deleted.

Save a request

  1. Build the request in the Request Builder.
  2. Press Ctrl+Alt+S (Cmd+Alt+S on macOS) or click 💾 Save.
  3. Type a name, such as Get user by ID, choose a collection, and click Save.

Saving again with the same name in the same collection updates that request instead of creating a copy.

What a saved request keeps:

SavedNot saved
Method, URL, params (including disabled rows), headers, body, notesSecret auth fields typed as real values: password, token, API key value, client secret. A field that only holds a {{VARIABLE}} is saved (details).
Auth type and non-secret auth fields
Pre-Request and Post-Response scripts
Retry count, timeout, SSL setting

Scripts in collections: a saved request keeps its script source, and the script runs when you press Send. Read any script in a collection someone else gave you before you run it, the same way you would a shell script.

Work with saved requests

To…Do this
Open a requestClick it, or use Edit Request
Copy a requestDuplicate Request creates Get user by ID (Copy) in the same collection
Delete a requestDelete Request (asks you to confirm)
Delete a whole collectionDelete Collection on the collection (asks you to confirm)

Favorites

Click ⭐ in the Request Builder toolbar to pin the current request. Favorites appear under Quick Actions → Favorites for one-click access. Click ⭐ again to unpin.

History

Every request you send is added to History, newest first. The icon tells you how it went:

IconMeaningShown next to it
🟡 spinningStill sendingSending…
🟢Got a response below 400200 312ms
🔴Got a 4xx or 5xx response404 120ms
🔴No response at all (network error, failed Pre-Request script, invalid URL)Failed (hover to see the error)
no colourRecorded by an older DotFetch version that didn't store the status

Cancelled requests are removed from History.

Things to know:

  • Variables are kept as written. History shows GET /users/{{USER_ID}}, not the filled-in value, so loading an entry back gives you the reusable request.
  • Click an entry to load it back into the Request Builder.
  • Scripts aren't stored in History. It only remembers that a request had scripts. Loading such an entry shows a note saying so. Save to a collection to keep scripts.
  • Secrets aren't stored, the same as for collections. {{VARIABLE}} references are kept.
  • Size limit: History keeps the last 50 requests. Change it with the dotfetch.maxHistory setting.
  • Clear History, in the History title bar, removes everything.

Where it's stored

Collections, favorites, and History are kept in VS Code's own extension storage on your machine. They aren't written into your project folder, so they don't end up in Git.

Collections, Favorites & History · DotFetch Docs | dotsuite