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 →

Plugins

A plugin is a single WebAssembly file. The same file runs in the Mac app, in the web app and in rt. It can change requests before sending, comment on responses, contribute tabs and bring importers – in a sandbox, with permissions you see before installing, and without ever seeing a secret value.

Edition
Free
Format
one .wasm file with an embedded manifest
Permissions
network (hosts), storage, variables
Manage
Manage plugins… in the command palette
Write
Rust with the plugin SDK

What a plugin can do

Extension pointWhen it runs
PrepareBefore every send, after authentication and before signing; it can change the request
ResponseAfter every response; it can add notes
TabsTabs in the request editor, the response or for the collection, drawn from declarative blocks (text, tables, trees, forms, buttons)
ImportersConvert files in the Import dialog and in rt import into a collection, with a loss report

Prepare and response also run in rt send and rt run, exactly as in the apps; tabs exist only in the apps. One example is the bundled OData plugin for SAP (OData and SAP): the SAP knowledge lives in the plugin, not in the core.

The sandbox

  • No native code: plugins are WebAssembly only and run in an interpreter that works the same everywhere.
  • No file system, no threads and no network except through the host’s HTTP call.
  • Every call runs in a fresh instance with a fuel limit and at most 64 MiB of memory.
  • Plugins never see secret values: requests and responses reach them masked.
  • If a plugin crashes, the host reports it as failed and keeps running.

Permissions

A plugin declares in its manifest what it needs, and you see that before installing it:

PermissionAllows
networkHTTP requests to the listed hosts only ({request} means the host of the request being sent)
storageA private key-value store per plugin and device
variablesReading the non-secret variables in scope

If an update asks for more permissions, RequestTailor asks again before granting them.

Install and manage

  1. Choose Manage plugins… in the command palette.
  2. Click Install from file… and pick the .wasm file.
  3. Check the requested permissions and confirm with Install.
  4. In the same dialog you switch plugins on and off or remove them with Remove.

Installed plugins live in the app’s data folder; the Mac app and rt share them. The web app keeps them in the browser. A switched-off plugin has no tabs, no hooks and no description. The bundled OData plugin is installed but off until you switch it on at first start or here later.

On the command line a plugin also runs without installing it:

rt send request.yml --plugin target/plugins/hello.wasm --pretty

Write a plugin

You write plugins in Rust with the plugin SDK and build them with one command from the core repository:

node scripts/build-plugins.mjs hello   # builds plugins/hello to target/plugins/hello.wasm

The full guide with an example, testing tools and versioning rules is in plugins/README.md, the binary interface in crates/rt-plugin/API.md. The plugin API is public and versioned. A TypeScript SDK has the types and a test host; building plugins from TypeScript is not available yet.

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

    OData plugin for S/4HANA, CAP and RAP ↑Product · RequestTailor core repository, plugins/odata, website/sap, website/docs/odata · checked on 2026-11-22

  2. 2

    Plugins only as WebAssembly, with permissions ↑Product · RequestTailor core repository, crates/rt-plugin/API.md, plugins/README.md · checked on 2026-11-22

Frequently asked

Short answers.

Can a plugin read my secrets?
No. Plugins see requests and responses only masked, and with the variables permission they read only the non-secret variables.
Do plugins run in the pipeline too?
Yes. The prepare and response hooks run in rt send and rt run exactly as in the apps; --plugin passes a file directly, --no-plugins turns the installed ones off.
Which language do I write a plugin in?
In Rust with the plugin SDK. For TypeScript there are the types and a test host, but no build to WebAssembly yet.

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.