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 →

rt command line

rt runs the same core as the apps: what is green in the app is green in the pipeline. The output is made for programs – JSON on stdout, exit codes a pipeline understands – and you pass secrets as pipeline variables, never in the files.

Edition
Free
Systems
macOS, Linux x86_64 and aarch64
Also
Docker image, GitHub Action
Output
JSON report, JUnit, text
Exit codes
0 to 4

The commands

CommandWhat for
rt sendSend one request; JSON report on stdout
rt runSend a collection or folder in order, with tests and assertions
rt importTurn other tools’ exports into a collection folder
rt scanCheck collection files for credentials
rt mockAnswer with the saved examples, as a mock server
rt docsWrite a static HTML page from the collection
rt mcp, rt approvals, rt approve, rt denyMCP server for AI agents and its approvals (AI agents and MCP server)
rt mcp-testRun saved MCP tests (MCP client)
rt agentCompanion for the web app (Companion rt agent)

rt --help and rt <command> --help show every option. The downloads for macOS and Linux are on the download page.

rt send

rt send <request-file> [--env NAME] [--var NAME=VALUE]... [--pretty]

The collection is the nearest folder above the request file that contains opencollection.yml.

OptionMeaning
-e, --env NAMEUse the environment NAME
--var NAME=VALUERuntime variable with the highest precedence, repeatable – for secrets from the pipeline or another host
--body-limit BYTESKeep at most this many body bytes in the report (default 10 MiB)
--plugin FILE.wasm, --no-pluginsAlso run a plugin, or do not run the installed ones
--cookie-jar FILESend cookies from the file and store new ones in it
--no-promptFail instead of waiting for an OAuth sign-in (pipelines)
--no-scriptsDo not run the collection’s scripts; assertions still run
--prettyIndent the JSON

The output is one JSON object, the send report: what went on the wire (secrets as ***), the response with status, headers, body and timing, the variables used and their origin, placeholders without a value, results of tests and assertions and any error. The web app produces the same report. WebSocket, gRPC and SSE (--sse) open sessions; see gRPC, WebSocket, SSE and GraphQL.

rt send health/status.yml --env CI --var token="$API_TOKEN" \
  | jq -e '.response.status == 200'

rt run

rt run sends every request of a collection or folder in order and reports tests and assertions – the command for pipelines. Variables that scripts set carry over to the following requests of the run, never into the files.

rt run                                     # the collection (or folder) you are in
rt run api/users -e Staging --var token=$API_TOKEN
rt run . --data users.csv --reporter junit=reports/junit.xml --reporter json=reports/run.json
OptionMeaning
--data FILECSV or JSON; each row is an iteration with its own variables
--iterations NSend the requests N times
--delay MSWait between requests
--bailStop at the first failure
--reporter NAME[=FILE]text, json or junit, repeatable

junit writes JUnit XML as GitHub, GitLab and Jenkins read it: a test suite per request, a test case per test and assertion. json holds the complete, masked rt send report for each step. text is always on, one line per request on stderr.

Exit codes

Codert sendrt run
0A response arrived, whatever its HTTP statusEvery request answered, every test and assertion passed
1No response: connection, DNS, TLS, timeout, too many redirectsNo network stack
2Usage error, no collection, invalid files, request not in the collectionUsage error, unknown environment, unreadable data file
3Request could not be prepared: unknown environment, invalid URL, auth failed, a plugin or script stopped itExternal secrets or plugins could not be set up
4A response arrived but a test or assertion failedA request, test or assertion failed

In a pipeline

Pass secrets as job variables to --var; never write them into the collection. With --no-prompt, an OAuth flow that needs a person fails instead of waiting.

GitHub Actions, with the action from the core repository:

- uses: clouddnagmbh/requesttailor/github-action@v1
  with:
    collection: api
    environment: Staging
    junit: reports/junit.xml
  env:
    RT_VAR_token: ${{ secrets.API_TOKEN }}

GitLab CI or any other environment with Docker, with the image ghcr.io/clouddnagmbh/rt (minimal, no shell, running as a non-root user):

docker run --rm -v "$PWD:/work" ghcr.io/clouddnagmbh/rt run . --reporter junit=junit.xml

rt import

rt import shop.postman_collection.json prod.postman_environment.json --out ./shop
rt import api.yaml --format openapi --out ./api --json

Prints the loss report. Exit code 0 once the collection is written, 2 if the input cannot be read or --out is not empty. Details in import on the command line.

rt scan

Finds credentials in collection files before they reach Git – the same scanner the app runs before every commit. Exit code 0 without findings, 1 with findings, 2 if a path cannot be read. A finding’s value is never printed. As a Git pre-commit hook (.git/hooks/pre-commit, executable):

#!/bin/sh
files=$(git diff --cached --name-only --diff-filter=ACMR -- '*.yml' '*.yaml' '*.json')
[ -z "$files" ] && exit 0
exec rt scan $files

rt mock and rt docs

Requests can keep saved examples: a request and the response it got (also carried over by the Postman import). rt mock answers with them, so the app, a front end or a test can work before the real service exists:

rt mock . --env Local --port 4010

An incoming request matches an example by method and path; when several fit, the one whose saved request matches best wins. Without a match there is a 404 with a list of all routes. The mock listens on 127.0.0.1 unless you pass --host.

rt docs . --out site writes a static HTML page with a stylesheet: folders, requests with method, URL, description, parameters, headers, body, auth type and examples. Secret values never appear; anything that looks like a credential is shown as ***.

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

    Runner, rt run, JUnit and JSON, exit code 4 ↑Product · RequestTailor core repository, crates/rt-core (runner, assert), crates/rt-cli/README.md (Exit codes) · checked on 2026-11-22

  2. 2

    rt mock and rt docs ↑Product · RequestTailor core repository, crates/rt-cli/src/mock.rs und docs.rs, launch/wave8/RELEASE-NOTES.md · checked on 2026-11-22

  3. 3

    macOS app, web app, rt for macOS and Linux ↑Product · RequestTailor core repository, launch/RELEASE-NOTES.md (Entwurf für das erste Release), crates/rt-cli/README.md · checked on 2026-11-22

Frequently asked

Short answers.

How do I run RequestTailor collections in CI?
With rt run, for example rt run api -e Staging --var token=$API_TOKEN --reporter junit=junit.xml. There is a GitHub Action and a Docker image; exit code 4 fails the build on failed tests.
Why exit code 0 for an HTTP error?
rt send reports 0 when a response arrived – a 404 or 500 too. Check the status with an assertion (then exit code 4) or with jq on the JSON report.
How do secrets get into the pipeline?
As job variables that you pass with --var; in the GitHub Action as RT_VAR_ plus the variable name, for example RT_VAR_token. You never write them into the collection files.

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.