// getting started
Getting Started
Resonance is a local-first, zero-account desktop API client. Nothing leaves your machine unless you send a request. No sign-in, no telemetry, no cloud sync — just install and start building.
Installation
Linux
- Download the AppImage or .deb from the Download section, or install from Flathub or the AUR (
yay -S resonance-bin) - AppImage: make it executable (
chmod +x Resonance*.AppImage) and run it - .deb: install with
sudo dpkg -i resonance*.deb
macOS
- Download the DMG (universal — Intel and Apple Silicon) or install via Homebrew:
brew install db-mobile/resonance/resonance - Open the DMG and drag Resonance to your Applications folder
Windows
- Download the NSIS installer and run it — no elevated permissions required
Making Your First Request
- Right-click in the collections sidebar and select New Collection, then New Request
- Choose an HTTP method and enter a URL, e.g.
https://api.example.com/users - Add headers, query parameters, or a body in the tabs below the URL bar
- Click Send Request
- Inspect the response — Body, Headers, Cookies, and Performance tabs are all available
Importing Collections
OpenAPI / Swagger
- Click Import in the collections sidebar header and choose OpenAPI Collection
- Select your OpenAPI 3.0 YAML or JSON file
- Resonance parses all endpoints, generates example bodies from schemas, and organises them by path
Postman Collection
- Click Import and choose Postman Collection
- Select a Postman v2.0 or v2.1 JSON file — request examples and auth settings are preserved
Postman Environment
- Click Import and choose Postman Environment
- All variables are imported into a new Resonance environment
Environments & Variables
- Open the environment selector dropdown in the sidebar and click Manage Environments…
- Click Add Environment, give it a name (e.g. Development), and add key-value pairs such as
baseUrl → https://api-dev.example.com - Select the environment from the dropdown to activate it
- Use
{{variableName}}anywhere in URLs, headers, or request bodies — values are substituted at send time, entirely locally
Dynamic variables like {{$uuid}} and {{$timestamp}} are generated fresh on every request without touching the environment.
Authentication
- Open the Authorization tab in the request panel
- Choose a type: Bearer Token, Basic Auth, API Key, OAuth 2.0, or Digest Auth
- Credentials are saved per-request and stored locally — they are never sent to any external service
- Reference sensitive values via environment variables:
{{token}}
Workspace Tabs
- Click + in the tab bar to open a new workspace tab
- Each tab holds its own URL, method, headers, body, and response state independently
- Switch tabs with
Ctrl/Cmd+1–9; open a new one withCtrl/Cmd+T - Tab state persists across application restarts — open exactly where you left off
Scripts
Open the Scripts tab in the request panel to write pre-request or test scripts in JavaScript. See Using Scripts for the full API reference.
Mock Server
Click the Mock Server toolbar action to spin up a local HTTP server backed by your OpenAPI collections. See Mock Server for setup details.
Keyboard Shortcuts
- Press
?anywhere to open the shortcuts reference Ctrl/Cmd+Enter— Send requestCtrl/Cmd+S— Save current endpointCtrl/Cmd+T— New workspace tabCtrl/Cmd+W— Close current tabCtrl/Cmd+,— Open settings
Exporting Code
- Right-click an endpoint or use the export button and select Export Code
- Choose from cURL, Python, JavaScript, Node.js, Go, PHP, Ruby, or Java
- The generated snippet copies to your clipboard
Next Steps
- Collection Runner — run sequences of requests and chain variables between steps
- Using Scripts — full pre-request and test script API reference
- Mock Server — serve OpenAPI-backed responses locally
- Issue tracker — report bugs or request features