Download

What you get on first run

The app opens seeded with two public demo servers — JSONPlaceholder and httpbin — plus an example OIDC provider, so you can send a request and watch history and timing fill in before configuring anything of your own.

Setting up your own API takes about a minute:

1. Configuration → Servers — add your API’s base URL.
2. Configuration → Auth Providers — add a provider. For OIDC, enter the issuer URL and press Discover; the endpoints and scopes fill themselves in. Point your server at the provider.
3. Type a path and press Send (or ⌘/Ctrl + Enter).
4. Bookmark the ones worth keeping into a collection.

Platform notes

Desktop — macOS, Windows, Linux. Everything is available, including interactive OIDC user login. Client secrets and bearer tokens are stored in the operating system’s own keychain, not in a settings file.

Phones and tablets — iOS, iPadOS, Android. The same feature set, in the phone layout: Request · Response · History · Servers as bottom tabs, with secrets in the system keystore.

Web. Nothing to install, with two differences worth knowing. Requests from a browser are subject to CORS, so an API that doesn’t send permissive headers has to be reached through a proxy. And interactive user login isn’t available in the browser — use client credentials or a static bearer token there.

Your data

Everything stays on your device by default — servers, auth configuration, history and collections — with secrets held in the OS keychain or keystore. If you’d rather have the same setup on every machine, point the app at your own cloud endpoint: a URL you control that speaks plain JSON. There’s no account to create either way.