Overview
Hoppscotch preserves API-development intent as requests move across browser, proxy, extension, native, Agent, team, self-hosted, sandbox, and CI environments. Versioned data, typed contracts, capability checks, local encryption, role-governed state, and host-mediated scripts keep the workflow portable without making runtimes identical. The repository supports an architecture-level reading, not claims about hosted reliability, performance, adoption, or a full security audit.
Learning outcomes
- Hoppscotch preserves API-workflow semantics through versioned data, typed contracts, and adapters, not identical runtimes.
- Execution paths should be chosen for concrete request constraints, with technical capability, convenience, and trust considered separately.
- Shared collections do not make runtime state shared: secrets, cookies, certificates, and local Agent settings retain distinct ownership.
- Sandbox and CLI reuse extends the workflow to scripts and CI, while the repository supports architecture claims rather than a full security or production verdict.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
What does Hoppscotch preserve across web, desktop, Agent, and CLI?
Hoppscotch preserves the request workflow's meaning—collections, variables, scripts, authentication, transport intent, responses, and selected state handling—while each runtime changes capabilities and local conditions.
When should an API request move beyond Hoppscotch's browser path?
Move beyond Hoppscotch's browser path when the request needs capabilities browser rules do not provide, such as client certificates, custom CAs, proxy authentication, or local access. Choose the smallest compatible boundary that meets the requirement.
Is Hoppscotch Agent a complete security guarantee?
No. Hoppscotch Agent implements a loopback, registered, encrypted browser-to-Agent payload boundary, but the repository does not prove a full security audit; the machine, browser, configuration, endpoint, and operating system remain in scope.
Can Hoppscotch collections run in CI?
Yes, supported collection and test semantics can run through the Hoppscotch CLI in CI, including scripts, inheritance, metrics, and reports. The CLI is alpha and does not reproduce browser cookies, desktop access, native certificate stores, or every interceptor capability.
What becomes shared when a Hoppscotch request joins a team?
A team workspace can share authorized collections, requests, environments, roles, and live change events, while secret values, cookies, certificates, Agent registrations, and machine-specific settings can remain local.