Everything it does, section by section.

Requests

A request editor with the pieces you reach for most, and nothing you have to dismiss first.

• GET, POST, PUT, PATCH, DELETE with query params, headers and a raw or JSON body.
• Friendlier body editor. Tab and Shift+Tab indent and outdent, Escape then Tab leaves the field, and Enter keeps your indentation.
• Real error messages. A failed request shows the underlying cause, such as DNS, connection refused or a TLS certificate problem, instead of a generic “fetch failed”.
• Instant startup. A small Electron app that opens straight to where you left off. No sign-in screen and no workspace picker.
• Private CA support. Trust an extra certificate for local mkcert setups and internal servers, from Settings.

Responses

Read the answer quickly, then get on with it.

{
  "id": 1,
  "email": "admin@example.com",
  "roles": ["admin"],
  "verified": true
}

Collections and folders

Choose a collection from a dropdown and the Requests panel shows only that collection. The icon sidebar is ordered Collections, Requests, Environments, History, and clicking the active icon collapses it.

• Collection overview. A Markdown description, a request summary you can filter by HTTP method, and a linked environment that is switched to when you select the collection.
• Folder view. Click a folder's name for a breadcrumb, rename, request and subfolder counts, its subfolders, and every request inside it with method filters and edit and delete buttons.
• Create in place. New request, New subfolder, Import request and Paste cURL, always into the folder you are looking at.
• Safe deletes. Deleting a folder or request asks for confirmation. A folder is removed with everything inside it.
• Collapsible folders in the sidebar, remembered between sessions.

Environments and variables

Use {{name}} in the URL, params, headers and body. Switch environment from the header to point the same collection at local, staging or production.

Capture rules

After a successful (2xx) response, a rule saves a value into a variable of the active environment. Read it from a JSON body path such as data.access_token or items[0].id, or from a response header.

Authentication

Auth is set per collection, on its Authentication tab. Requests inherit it, any request can opt out with “No auth”, and sign-in refreshes itself when a token runs out.

Request docs

Describe what an endpoint does next to the request that calls it.

• Markdown everywhere. Collection and request descriptions render by default; click the pencil to edit.
• Argument list. Note each argument's location, whether it is required or optional, its default and what it means. “Add from request” fills the list from the request's params and headers.
• Read-only context. The Docs tab shows the request's method and URL alongside.

cURL and sharing

Move requests between ScratchAPI, your terminal and your teammates without an account in the middle.

# Copy as cURL
curl -X POST \
  -H 'Content-Type: application/json' \
  -d '{"email":"admin@example.com"}' \
  'https://api.example.com/auth/login'

History

Every sent request is stored with its response, so yesterday's answer is still there today.

• Read-only replay. Open an entry to see the request as sent, its outcome and the stored response, including headers and body (bodies are capped at 256 KB per entry).
• Take it with you. Copy a history entry as cURL, or save it into a collection, which defaults to its original one.
• Tidy by design. History keeps the most recent 20 entries and drops the oldest. Inherited auth is added at send time, so tokens are not written into history entries.

Storage and privacy

Collections, environments, history and settings are readable JSON in the app's data folder (~/.config/scratchapi/ on Linux), with 2-space indentation and stable key order, so diffs stay clean.