Getman
العربيةDownload

Features

What Getman does today. Everything on this page exists in the current build.

Requests

  • REST requests with JSON, text, XML, form, multipart (text and file parts), binary or GraphQL bodies
  • WebSocket (text and binary frames received) and Server-Sent Events
  • Path parameters, query parameters, headers and cookies
  • Proxy URL and a custom CA certificate
  • Request history, response examples and an API docs view

Collections and environments

  • Projects, collections and folders with drag-and-drop order
  • Local, development, staging, production and other environment kinds
  • Variables with a clear precedence: runtime, environment, collection, project, global
  • Secret variables, masked on screen and encrypted at rest
  • A confirmation before a request that can change data reaches production

Auth

  • Bearer, Basic, API key (header or query), cookie and custom headers
  • OAuth 2.0: client credentials, password, authorization code with PKCE, refresh token
  • Set once on the project; collections, folders and requests inherit or override it

Testing

  • Assertions without code: status, response time, JSON field exists, equals, length, header, body contains, JSON Schema
  • Extractors from body, header, cookie or status into runtime, environment, collection or global variables
  • Pre-request and test scripts in a QuickJS sandbox (32 MB memory, 5 s default timeout)
  • Collection runner with iterations, delays, data files and per-step results

Contracts and design

  • OpenAPI 3.1 export from your saved requests
  • Contract comparison with breaking, potentially breaking, non-breaking and unknown ratings
  • OpenAPI editor: outline, forms, raw JSON or YAML, validation
  • Local mock server from saved examples or an OpenAPI file
  • Import Postman v2.1 collections and environments, OpenAPI 3, Swagger 2, HAR 1.2 and cURL
  • Export to Postman v2.1, OpenAPI 3.1 or a Getman workspace
  • Code snippets: Fetch, Axios and cURL

Team and Git

  • A getman/ folder in your existing repository: one YAML file per request
  • Fetch, Pull (fast-forward only), Commit and Push from the app, using your installed Git
  • Conflict markers and invalid files are refused on load
  • API change packages with contract diff, examples, migration notes and evidence
  • Integration Inbox, Completed list and Timeline
  • Seven verification labels, from Not tested to Integration verified

CLI and agents

  • getman run for requests, folders and collections, with JSON output and CI exit codes
  • getman contract export and diff --fail-on breaking
  • getman change new, list, show, verify, report and validate
  • getman mock to serve examples from the terminal
  • getman mcp: a local MCP server with 11 read and 4 write tools
  • Per-request approval of production writes from agents
  • --read-only mode and workspace scoping
Collaborate through Git

One API change, from backend to frontend.

A change package travels with the code, through the Git repository your team already uses. Step through a real handoff.

  1. Backend developer
  2. Getman
  3. Git
  4. Frontend developer
  5. Coding agent

  1. In the Shop API, Alice renames total to totalCents and adds currency to GET /orders/{id}, then updates the saved request in Getman.

  2. Getman compares the OpenAPI 3.1 contract with the previous one. The new fields are non-breaking. Removing total is rated potentially breaking, because that response schema was inferred from examples, which is weak evidence.

  3. Changes → New change package. It records the endpoint, the contract diff, examples and the migration note “Read totalCents (integer cents) and currency; total is gone.” Its reference is GT-SHOP-001.

  4. Verify now runs the affected requests against the running API. The result is recorded in the package. Nobody types in a pass.

  5. Alice commits the code and the getman/ folder together and pushes. No Getman server is involved.

  6. Bob clicks Fetch. Getman reads the incoming commits and lists the package before he pulls.

  7. With I integrate as set to web, the package lands in Bob's Inbox with its severity and evidence.

  8. Bob gives his coding agent the reference. Through MCP it calls list_changes and get_change and reads the diff and examples.

  9. The agent updates the web client and its tests in Bob's repository, using the examples from the package.

  10. report_integration runs the requests first. verified is accepted only with a passing run against the current contract. After a pull, Alice sees Integration verified.

Everything here happens on two laptops and one Git remote. Getman has no cloud service.

Keyboard shortcuts

Mod is ⌘ on macOS and Ctrl on Windows.

Command palette⌘KCtrlK
Find a request⌘PCtrlP
Send the request⌘↩CtrlEnter
Cancel the request⌘.Ctrl.
Save⌘SCtrlS
New request⌘NCtrlN
Import⌘OCtrlO
Focus the URL⌘LCtrlL
Changes view⌘⇧GCtrlShiftG
Copy as cURL⌘⇧CCtrlShiftC
Switch the response split⌘⇧LCtrlShiftL
Show or hide the sidebar⌘BCtrlB

All keyboard shortcuts

Not in Getman today

Planned or deliberately deferred. None of this is available now.