An API client where your team's requests stay on your team's server

DialCatz is a free, open-source API client for REST, GraphQL and WebSocket, with a self-hosted team server called DialCatz Den. macOS, Windows and Linux.

An API client ends up holding a lot of sensitive things: base URLs of internal services, tokens, the shape of every endpoint you have. When a team shares that, it usually lives on someone else's server.

DialCatz keeps it on yours. It is a free, open-source (GPL-3.0) API client for macOS, Windows and Linux — and when you want to share, DialCatz Den is a small server your team runs itself.

Every kind of call
REST and GraphQL — params that stay in sync with the URL, headers, JSON / XML / form / multipart / binary bodies, and Bearer, Basic or API-key auth set once on a folder and inherited below
WebSocket — connect, send, and a live log, next to the REST calls that open the socket
Paste a cURL into the address bar and it becomes a request; every request turns back into cURL or fetch
Requests leave from the app itself, not a browser: no CORS in the way, and local https://*.localhost sites are trusted
Responses are readable: a JSON tree you can fold and search, a table view, image and PDF previews, hex and base64, the cookies, and the timing of every call.

Collections that behave
Folders, drag and drop, favourites, environments with variables, globals, pre-request and test scripts (pm.* scripts from Postman work too), and a runner with iterations whose results export as JSON or JUnit XML. Deleting a collection asks for its name typed out, so a stray click never costs you an afternoon.

Moving in is one step: Postman collections, environments and whole data exports (or straight from your Postman workspaces with an API key), OpenAPI / Swagger, and cURL.

Sharing, two ways
DialCatz Den — one small Go container with SQLite or PostgreSQL. Live sync, invite links instead of accounts, per-person tokens you can revoke, and an admin panel for members and workspaces. The part I care about most: environment values stay on each computer. The Den only ever receives variable names, so a teammate's production token never sits on the server.

Or plain Git — keep a workspace as files in your repository and share it with commits, no server at all.

AI, only on your say-so
Explain a confusing 422 or a CORS error, write the tests for the response you just got, generate a body with realistic fake data, or ask in plain words for "a request that creates an order". Names and URLs are sent, never your environment values, and tokens or JWTs are masked first. Off until you add your own key.

Better with DevCatz
Every DevCatz site arrives in DialCatz as an environment, and a Laravel or Goravel app's routes come in as requests. Check in DBCatz opens the table a request touched in DBCatz.

The whole family working together, in two and a half minutes:

Try it
Download: catzoid.com/dialcatz/download — macOS (signed and notarized), Windows, Linux x64 and ARM64
Run your own Den: catzoid.com/docs/dialcatz-den
Source: github.com/catzoidhub/DialCatz · DialCatz Den (AGPL-3.0)
Made in Indonesia by a small team, written with Claude. Feedback and issues are very welcome.