Testnizer — The offline API client
Offline, open-source API client. Your data never leaves.
3 followers
Offline, open-source API client. Your data never leaves.
3 followers
A free, standalone desktop API client (REST, SOAP, GraphQL, gRPC, WebSocket & more) that runs 100% offline. Collections stay in local SQLite, tokens in your OS keychain — nothing ever goes to a vendor cloud. Built-in offline dev tools. Open source (MIT).
Free
Launch Team
Render: Get up to $100K in startup creditsThe fastest way to launch and scale your startup in the cloud
Promoted
finally a desktop api client that doesn't nag me to sign up. love that collections live in sqlite and secrets stay in the keychain. one thing i'd really appreciate is a built-in mock server so i can stub responses from my saved collections and let the frontend dev hit them without spinning up anything else.
Thanks — though the no-signup part is more a side effect than the goal. What we actually wanted was: nothing goes to a cloud, it all stays on your machine, it stays secure, and everything I need for API work lives in one place. The SQLite storage and the keychain handling you noticed are just that decision showing through.
Which is also why the mock server is already in there — "one place" wouldn't mean much if stubbing a response sent you somewhere else. That you assumed it wasn't is on us, not on you; we've clearly buried it too well.
Right-click a request, a folder, or the project root → Create Mock Server from this…. It scaffolds the routes off your saved collection (method + path, :id params included) and runs inside the app, so there's nothing extra to start. Set the bind host to 0.0.0.0 and your frontend dev can hit it across the LAN.
One honest caveat: it mirrors the URL surface, not the bodies. If you'd rather not write those by hand, point Proxy unmatched requests to upstream at the real API with Record proxied responses as new endpoints switched on — one pass and the stubs come back filled with real payloads.
1.5 pushes further in the same direction. It's mostly a security release — keystores, JWT/JOSE, SAML, TLS inspection, all of it offline — and the mock server picks some of that up: it can serve a JWKS at /.well-known/jwks.json, so a service under test can fetch your keys from it.