Getman
العربيةDownload

API changes that arrive tested.

Getman is a desktop API client that runs entirely on your machine. Build and test requests, then hand every API change to your frontend team, and their coding agents, through the Git repository you already use.

Download GetmanWatch the tutorial

Desktop app for macOS and Windows. No account, no subscription.

The Getman window: a saved GET request to the Shop API with a 200 OK JSON response, its status, time and size.
Build and test

The API client you know, without the cloud.

Requests, collections and environments live on your machine. Everything you need for daily API work is there from the first launch.

  1. Every kind of request

    REST with JSON, form, multipart, XML, binary or GraphQL bodies, plus WebSocket and Server-Sent Events, from one request builder.

  2. Auth you set once

    Bearer, Basic, API key, OAuth 2.0 with PKCE, cookies or custom headers on the project. Collections, folders and requests inherit it and can override it.

  3. Environments that tell you where you are

    Local, development, staging and production, switched from the title bar. A request that can change data on a production server asks before it is sent.

  4. Assertions without code

    Check status, response time, JSON fields, headers, array lengths or a JSON Schema. Extract values into variables for the next request.

  5. Run a whole collection

    Run folders or collections in order, carry extracted values from step to step, and see every check that passed or failed.

  6. Scripts in a sandbox

    Pre-request and test scripts run in an isolated QuickJS sandbox with memory and time limits.

Beyond the desktop

The same engine in your terminal, your CI and your agent.

The getman command runs saved requests through the exact engine the app uses. A local MCP server gives coding agents the same reach, inside limits you set.

A CLI for scripts and CI
Run a request, a folder or a collection with any environment. Human output for you, JSON for pipelines, and exit codes CI can trust. Read the docs
A local MCP server for coding agents
Claude Code and other MCP clients can list requests, read the contract, run requests and create change packages. Secrets stay in your environment and are scrubbed from every answer. Read the docs
Production stays guarded
An agent's POST, PUT, PATCH or DELETE to a production environment needs your approval, one request at a time. --read-only removes every write tool.
$ getman run "Shop API" --workspace getman --env Local
Running Shop API · project Shop · env Local
  ✓ POST    http://127.0.0.1:4321/auth/login  200 OK  654 ms  67 B
      ✓ Status is 200
      ✓ accessToken exists
  ✓ GET     http://127.0.0.1:4321/products  200 OK  3 ms  111 B
      ✓ Status is 200
      ✓ $ length is at least 1
  ✓ GET     http://127.0.0.1:4321/orders/o1  200 OK  10 ms  104 B
      ✓ Status is 200
      ✓ total exists
      ✓ Response time is under 1000 ms
3 requests: 3 passed · 0 failed · 0 errors · 0 skipped · 670 ms (exit 0)
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.

Design and understand APIs

Contracts you can read, compare and mock.

Export an OpenAPI 3.1 contract from your requests, see exactly what changed between two versions, and serve examples locally before the backend is ready.

Breaking-change detection

Contract comparison rates every change as breaking, potentially breaking, non-breaking or unknown, separately for requests and responses.

OpenAPI editor

An outline, forms and raw JSON or YAML, with validation, import and export.

Local mock server

Serve saved examples or an OpenAPI file on 127.0.0.1, with status, headers, delay and a hit log.

HAR and Postman import

Bring in HAR captures, Postman collections and environments, OpenAPI 3 or Swagger 2, or paste a cURL command.

  • Postman v2.1
  • OpenAPI 3
  • Swagger 2
  • HAR 1.2
  • cURL

Fetch and Axios snippets

Generate client code with inherited auth and headers included and secrets masked.

Learn more: Features

Local-first by design

Your machine. Your repository. Nothing in between.

Getman has no account, no sync service and no telemetry. Team collaboration uses the Git hosting you already pay for, or don't.

In your Git repository

  • getman.yamlproject auth and headers, without secrets
  • environments/*.yamlvariable names, with secret values left blank
  • collections/**.yamlone file per request
  • contracts/openapi.yamlthe current contract
  • changes/GT-…yamlchange packages with evidence and status

Only on your machine

  • Secret values, encrypted with AES-256-GCM
  • The encryption key, in your system keychain
  • History, cookies and responses
  • The app database, in your user data folder

Agents get secrets from GETMAN_VAR_<KEY> in the shell that starts them, and never see them in tool output.

Security and privacy
Tutorial

Learn Getman, start to finish.

A narrated tour: install, everyday API work, what Getman keeps in Git, connecting a coding agent, and one real change from backend to frontend.

Getman onboarding

Duration: Narration uses a macOS system voice.Playing loads YouTube, which sets its own cookies.

Read the transcriptCaptions (WebVTT)Read the written guide

Chapters

Start on your own

  1. Download Getman
  2. Open a project or import a collection
  3. Send your first request
Getting started

Bring your team

  1. Link the getman/ folder in your repository
  2. Connect your coding agent through MCP
  3. Share your first change package
Team workflow

Questions, answered

What is Getman?

A desktop API client for macOS and Windows. You build, test and document requests like in Postman, and you hand API changes to other developers and their coding agents through Git, as change packages with real test evidence.

Is Getman free?

Getman has no price, no subscription and no account. You download it and use it.

Do I need an account?

No. There is no Getman account or server. Your data stays on your machine, and teams share through their own Git repository.

Does it work offline?

Yes. Getman needs a network only to reach the APIs you call and, if you use it, your Git remote.

Can my team use Git?

Yes, that is how teams work together in Getman. Link the getman/ folder in your repository. Getman uses your installed Git with your SSH keys and credentials, and never commits, pushes or merges on its own.

Does MCP require an AI API key?

No. Getman's MCP server runs locally and calls no AI service. Your coding agent (for example Claude Code) uses its own account; Getman only answers its tool calls.

How do I connect Claude Code?

Install the command-line tool from the app, commit a .mcp.json that runs getman mcp --workspace getman, export the secrets the requests need as GETMAN_VAR_<KEY>, and start claude at the repository root.

Does Getman support macOS and Windows?

Yes. macOS gets a universal app for Apple silicon and Intel. The Windows installers are built by CI but haven't been tested on a real Windows machine yet.

How are secrets handled?

Secret values are encrypted with AES-256-GCM, with the key in your system keychain. They are written to Git as blanks, never exported, masked on screen and scrubbed from CLI and MCP output.

How do I update?

Download the new version and install it over the old one. Getman doesn't update itself yet.

How does it compare to Postman or Apidog?

The everyday request work is similar. Getman is local-first: no account and no cloud workspace. It adds change packages, contract diffs, verification evidence and an MCP server, so API changes reach the frontend and its agents through Git. It imports Postman collections and environments, and OpenAPI files from any tool.

What is a change package?

A YAML file in your repository that describes one API change: the affected endpoints, the contract diff and its severity, examples, migration notes, evidence from real test runs and each consumer's integration status. It has a reference like GT-SHOP-001 that people and agents can use.

Send your first request.

Free to use, nothing to sign up for. Your requests stay on your machine.

Download Getman

Desktop app for macOS and Windows. No account, no subscription.