RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →

Sending requests

Request at the top, response below. You edit method, URL, parameters, headers, body and auth, send with Mod+Enter and see status, time, size, headers, tests and the formatted body. Large responses stay in the core; the interface loads only the lines you are looking at.

Edition
Free
Send
Mod+Enter or Send
Request tabs
Params, Headers, Body, Auth, Vars, Scripts, Assertions
Response tabs
Body, Headers, Tests, Console, Timing
Views
Pretty, Raw, Tree, Hex

The request

Request editor with POST, URL baseUrl/users, the resolved address below, tabs Params, Headers, Body json, Auth bearer, Vars, Scripts, Assertions and a JSON body
The request editor: method and URL, the resolved address below and the tabs.
  1. Method and URL. Variables such as {{baseUrl}} are highlighted; the resolved address is shown below.
  2. Send with its shortcut next to it.
  3. The tabs Params, Headers, Body, Auth, Vars, Scripts and Assertions. Small badges show what is set, such as json or bearer.
  4. Under Body you choose the kind (for example JSON); Format indents it (Shift+Alt+F).

The URL is the truth for the query string: the rows under Params mirror it, path parameters fill segments such as :id. How authentication works is in Authentication; scripts and assertions in Scripts, tests and runner.

Send

  1. Choose the environment at the top right.
  2. Open the request in the Requests sidebar.
  3. Press Mod+Enter or click Send.
  4. The response appears below the request. Unsaved changes are sent too; they are saved only with Mod+S.

When sending, the core prepares the request – variables, inherited settings, auth, body –, fetches a token for OAuth 2.0, runs active plugins and scripts and sends it over the wire. The report of the send is the same everywhere: in the app, in the web app and as JSON from rt send. Secret values appear in it only as ***.

The response

Response with 200 OK, Time 14 ms, Size 143 B, HTTP/1.1, tabs Body, Headers, Tests, Console, Timing, views Pretty, Raw, Tree, Hex, a JSONPath filter and formatted JSON
The response with status line, tabs, views and JSONPath filter.
  1. Status line: status, Time, Size and HTTP version.
  2. Tabs Body, Headers, Tests, Console (script output) and Timing.
  3. Body views: Pretty (formatted and foldable), Raw, Tree and Hex.
  4. A JSONPath filter such as $.items[*].id shows only the matching parts; Copy copies the body.

Large responses

Large responses stay on the Rust side in a response store; the interface fetches only the lines on screen. That a 100 MB response renders and scrolls without stutter is one of the performance budgets that every build measures.

History and cookies

History in the sidebar lists the requests you sent with name, method, masked URL, status and time. The history keeps no bodies and no header values. Cookies set by responses are kept per collection and environment and sent again; Show cookies… in the command palette shows them. Cookie values are masked in the report.

Typical problems

What you seeWhat helps
A variable stays in the URL as {{name}}It has no value in any layer. Check the environment; the report lists such placeholders under unresolved (Environments and variables).
The web app says the browser blocked the requestThe server sends no CORS headers. Start and pair the rt agent companion (Companion rt agent).
TLS error with a client certificate in the web appBrowsers do not present client certificates for web pages. Use the Mac app or rt.

See also

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    Secrets in the keychain and from external vaults ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip 3), crates/rt-cli/README.md (externe Secrets), website/docs/environments · checked on 2026-11-22

  2. 2

    Large responses stay in the core ↑Product · RequestTailor core repository, CLAUDE.md (App, ResponseStore), perf/README.md · checked on 2026-11-22

  3. 3

    Performance budgets as release gates ↑Product · RequestTailor core repository, perf/budgets.toml, perf/README.md · checked on 2026-11-22

Frequently asked

Short answers.

How do I send a request in RequestTailor?
Open the request in the sidebar and press Mod+Enter (⌘↩ on the Mac, Ctrl+Enter on Windows and Linux) or click Send.
Can I filter a JSON response?
Yes. A JSONPath filter sits above the body, for example $.items[*].id. There are also the views Pretty, Raw, Tree and Hex.
How large can a response be?
Large responses stay in the core and the interface loads only visible lines. A 100 MB response renders and scrolls without stutter; that is a release gate.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.