Quick Request · Index

This is the UI handbook for Quick Request. Tap buttons, fill forms and write scripts in the app — without ever touching a raw JSON field.

Reading Path

Chapter	What it solves
quick-start	First launch: create a group, set up an environment, send your first request
concepts	Why does a request containing only /echo still work? Where does {{x}} get its value?
scripting	What scripts can change, and how to add a pre-send / post-response script in the UI
recipes	Auto-attach token after login, request-body encryption, assertions, random data — ready-made recipes
http · websocket · tcp · udp · grpc · mqtt	How to configure and use each protocol in the UI, plus gotchas
Script API Reference	JavaScript API signatures for Quick Request / rewrite scripts (on-site docs)
faq	Troubleshooting: can't connect, 401, garbled text, variable not resolved, etc.

The Global Mental Model (One Picture)

A group is bound to one environment; the environment provides a base address ("Pre-URL") for each protocol; requests store only relative paths and parameters. When you hit Send, the assembly pipeline combines the three into a real request, and runs the Action Chain (scripts / extraction / assertions) before and after the network call.

Key point: seeing /echo instead of http://host/echo in a request is not an omission — the host/port/scheme come from the bound environment's Pre-URL. Switching between dev/staging/production means editing one environment only, and the whole group follows. See concepts.

Glossary

Term	One-line meaning
Group	A folder of requests; the environment is bound to the group and shared by all requests in it
Environment	A set of "Pre-URLs + variables + cookie policy" representing one deployment target
Pre-URL	The base address the environment defines for each protocol; its scheme decides the protocol and whether TLS is used
Request	A single API call storing a path fragment, method, headers, body, auth and pre/post scripts
Action Chain	Ordered pre-send / post-response steps: scripts, library scripts, extraction, assertions, waits
Variable layers	Environment variables (persistent) / runtime variables (in-memory, cross-request) / per-send variables (one shot)