Gud API

Appearance

Collections ​

Collections let you save requests in a tree: folders, subfolders, and named requests. They are the main way to reuse work across sessions.

Save a request ​

When you have a request you want to keep:

  1. Click Save (or the equivalent action in the request panel).
  2. In the Save dialog, choose a collection and optional folder. The folder picker shows path labels so you can place the request at the correct depth.
  3. Give the request a name.

You can open any saved request from the sidebar to load it back into the builder.

Folders ​

Create folders to mirror APIs, teams, or environments (e.g. Auth, Users, Payments). Folders support nested sub-folders at any depth, so you can organize large projects however you like -- for example Payments / Stripe / Webhooks.

Timing sparkline ​

Saved requests display a small sparkline chart in the sidebar showing recent response times. This gives you a quick visual indicator of whether a particular endpoint is responding faster or slower than usual without opening the full response viewer.

Rename and delete ​

Use the sidebar context actions to rename or delete requests and folders. Deleting a folder removes its children -- confirm when prompted.

Collection variables ​

Variables can exist at the collection level (for example after importing from Postman). They participate in resolution together with environment variables. Environment values override collection values when both define the same key. See Environments & variables.

Shared collections ​

With a Team plan, you can share a collection with your team so everyone works from the same set of requests.

  • Right-click a collection in the sidebar and select Share with Team.
  • Choose a permission level: read/write (all members can edit) or read-only (only the owner can edit).
  • Shared collections show a people icon in the sidebar. Read-only collections additionally show a lock icon.

Non-owners of a read-only collection can view and send requests but cannot save changes. See Sync & teams for full details on team setup and permissions.