Skip to main content

Request bodies

For requests that send data — POST, PUT, PATCH — the Body tab picks what to send. Choose a type from the radio row, and Trq sets the matching Content-Type for you.

The Body tab — None / JSON / Raw / Form / Multipart / GraphQL radios with a JSON editor

Body types​

  • None — no request body (the default for GET/DELETE).
  • JSON — a JSON editor with line numbers; sent as application/json. Values are templatable — "ref": "{{var.applicationId}}". Hit Beautify to reformat, or ＋ Template ▾ to insert a token.
  • Raw — any text, sent verbatim; you control the Content-Type via a header.
  • Form — key/value rows sent as application/x-www-form-urlencoded.
  • Multipart — key/value rows sent as multipart/form-data, where each field is either Text or a File. Pick a file and Trq adds it to the project's file pool so the upload replays anywhere, including CI. Great for upload endpoints.
  • GraphQL — a Query field and a Variables (JSON) field, sent as a JSON POST of { query, variables } with Content-Type: application/json.

Beautify​

On the JSON and Raw editors, Beautify reformats the body in place — fixing indentation and quoting. It parses strict JSON first, then falls back to a lenient normalize (unquoted keys, single quotes, trailing commas) so a pasted-in snippet still tidies up; if it truly can't parse, it tells you rather than mangling the text.

Content-Type​

Each body type sets its own Content-Type, so you don't add one manually — except Raw, where you set it yourself. For Multipart, Trq lets the runtime write the multipart/form-data boundary, so don't override it by hand.

Next: assert on the response, or extract values to chain into the next request.