Skip to main content

Quick Start · Your First Request in Three Steps

Goal: build a working HTTP request from scratch. Once you understand the main line "Group → Environment → Request", every other protocol is just a different protocol and a different Pre-URL.

Step 1: Create a Group, Bind an Environment​

In Quick Request, the environment is bound to the group, and all requests in the group share it.

  1. Create a new group (e.g. My First Group).
  2. Bind an environment to the group. If you don't have one yet, create an environment first (e.g. Local).

Why the extra layer? Because when a module moves between dev / staging / production, you only want to edit the environment — not dozens of requests.

Step 2: Fill in the Pre-URL in the Environment​

An environment keeps one base address per protocol. To send HTTP, fill in the http entry:

Protocol lineExample base addressNotes
HTTPhttp://127.0.0.1:18080Use https:// to enable TLS
WebSocketws://127.0.0.1:18085Use wss:// to enable TLS
gRPCgrpc://127.0.0.1:18089Use grpcs:// to enable TLS
MQTTmqtt://127.0.0.1:18884Use mqtts:// to enable TLS

⚠️ The easiest pitfall: which protocol a base address belongs to is decided by the scheme at the start of the URL, not by which line you typed it into. A WebSocket base address must be written as ws://… or wss://…; if you accidentally type https://…, it is treated as HTTP, the WebSocket request finds no base address and fails. Keep the protocol line and the scheme consistent.

(The ports like 18080 above come from the sample test server; replace them with your real addresses when testing your own APIs.)

Step 3: Create a Request, Fill in Only the Path Fragment, Send​

Create a request inside the group:

  1. Protocol: HTTP; Method: GET.
  2. URL — fill in only the path fragment: /echo (not the full host — the host is already provided by the environment's http Pre-URL).
  3. Tap Send.

You'll see /echo echo back exactly what you sent. What actually went over the wire was http://127.0.0.1:18080/echo.

It Works — What's Next?​

  • Want to understand "why only /echo" and "where {{x}} comes from" → concepts
  • Want to sign requests before sending / decrypt responses → scripting
  • Want to copy a "login for token, auto-attach for the whole group" recipe → recipes
  • Switch protocol (WS/TCP/UDP/gRPC/MQTT) → the matching protocol page (see the index)