Hoppscotch Desktop
A cross-platform Tauri client for API development that supports REST, GraphQL, WebSocket, SSE, Socket.IO, MQTT and client certificates.
What Hoppscotch Desktop is for
Hoppscotch Desktop offers a desktop workspace for creating requests, collections and environments across REST, GraphQL, WebSocket, SSE, Socket.IO and MQTT workflows. It is useful for repeatable API checks, but the client, a cloud workspace and a local agent are separate components with different trust boundaries.
Start with a safe request
Use a read-only test endpoint first and inspect status, headers, response body and timing. Keep production write, delete and payment requests out of the first collection. Environment variables make a request portable, while secrets should stay local and should not be committed to a shared collection.
Review certificates and synchronization
Client certificates, self-signed roots, proxies and local agents can change what the application can reach. Add them only for a clear test case and document their scope. When connecting a cloud or self-hosted workspace, decide which collections, variables and history may be synchronized.
Maintenance note
This page covers Hoppscotch Desktop, standalone API requests, environments, certificates and local data boundaries. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Hoppscotch Desktop to this cloud drive
Baidu Netdisk
Save Hoppscotch Desktop to this cloud drive
Hoppscotch Desktop installation and first API request
Install the matching build, send a harmless request in standalone mode and verify environment, certificate and data settings before importing real work.
Before you start
- Choose the Windows, macOS or Linux package that matches the processor architecture.
- Prepare a non-destructive test endpoint and avoid real production credentials during the first run.
- If using an internal service or client certificate, confirm the expected trust chain and minimum permission with its administrator.
Installation steps
- 01
Install the platform package
Select the correct installer or archive, launch it and confirm the application version and local data directory before creating a collection.
- 02
Choose standalone or connected mode
Use standalone mode for local testing; add a cloud or self-hosted workspace only when synchronization or team features are needed.
- 03
Protect local variables
Put hosts and test tokens in environment variables, mark sensitive values as secret and ensure shared requests contain no real credentials.
Quick start
- 01
Send a read-only request
Create a GET request to the test endpoint, then inspect the status code, headers, body and response time rather than relying on a visual page result.
- 02
Save a collection and environment
Give the collection clear names, extract the host into an environment variable and resend after switching environments to confirm resolution.
- 03
Test advanced protocols deliberately
Add a WebSocket, SSE, MQTT or client-certificate request only after the basic request works. Do not disable TLS verification globally for troubleshooting.
Usage tips
- Standalone collections, history and local secrets rely on the operating system account and disk protection.
- A connected workspace can synchronize ordinary data to a server; keep sensitive variables local when the product supports that option.
- Review exported collections and debug logs for hostnames, query values and tokens before sharing them.
Troubleshooting and uninstall
Why does a request return 401, 403 or not-found?
Check the selected environment, host, path, method, token owner, project permission and server-side route. A web subscription does not automatically grant API access.
Why can the desktop client not reach an internal endpoint?
Check the local network, proxy, DNS, firewall, certificate trust and whether an agent is required. Test from the same machine with a minimal request before widening access.
- Export only required collectionsRemove real tokens from exports, sign out of connected workspaces and confirm whether synchronization still retains a server copy.
- Remove the client and local dataUninstall through the operating system and clear cache or history only after confirming that required collections and environment notes are backed up.
Frequently asked questions
Can Hoppscotch Desktop work without an account?
Standalone mode can create local requests, collections, environments and history. Cloud or self-hosted workspaces add synchronization and team features.
Is Desktop the same as Hoppscotch Agent?
No. Desktop is a full Tauri client; Agent is a local relay for browser-based workflows such as private networks and client certificates.
Should TLS verification be disabled to fix a certificate error?
Keep verification enabled for normal use. Check the certificate chain, hostname, proxy and local trust store, then limit any diagnostic exception to a controlled test.