Skip to main content

Building requests

Every request in an API session is built the same way: a method, a URL, and optional params, headers, auth, and body in the tabs below. Everything is templatable — anywhere you can type, you can drop a {{...}} token.

The request builder — method chip, URL, cURL / Template / Send, and the request tabs

Method & URL​

Click the method chip to choose the verb — GET, POST, PUT, PATCH, or DELETE. Each is color-coded so a list of requests reads at a glance.

Type the full URL in the bar next to it. The URL accepts templates, so a base can come from an environment:

GET  {{env.baseUrl}}/users/{{var.userId}}

Three buttons sit at the end of the URL bar, in order: ⤓ cURL, ＋ Template ▾, and Send ▸.

Query params​

Open the Params tab to add ?key=value pairs as rows instead of hand-editing the URL. Each row has an enable checkbox, a key, and a value (templatable). Disabled rows stay in the list but aren't sent — handy for toggling an optional filter. Params you add here and any already in the URL are merged when the request fires.

Headers​

The Headers tab is a key/value list, with autosuggest for common header names and values as you type — start typing Con… and pick Content-Type, then application/json. Values are templatable, so an auth header can reference a captured token:

Authorization: Bearer {{var.token}}

For the standard auth schemes, prefer the Auth tab — it materializes the right header (or query param) for you.

Insert a template​

The ＋ Template ▾ button (on the URL bar, and on the Body tab strip) opens a menu of everything you can reference — reusable variables like {{uuid}} and {{timestamp}}, captured variables under a Captured category, and environment values — so you click to insert instead of remembering names. Typing {{ opens the same menu inline.

Import from cURL​

Already have a request as a curl command — copied from your terminal, an API doc, or a browser's Copy as cURL? Click ⤓ cURL, paste it, and Import. Trq fills the method, URL, headers, and body from the command, so you don't rebuild it by hand.

Send vs Run​

  • Send ▸ fires this one request immediately and shows its response — that's for authoring: you see real data while you build, so you know what to assert on or extract.
  • ▶ Run (in the toolbar) replays every request in the session as a case, passing variables down the chain. See Running a case.

Next: add authentication, pick a body type, or chain requests with variables.