rq.visualizer (Response visualization)

The rq.visualizer namespace lets your scripts render a custom view of your response: a chart, a table, or any formatted HTML, shown right beside the raw body. You give it a Handlebars template and some JSON data, and Requestly renders the result in the response Body area behind a Visualize button.

rq.visualizer.set(template, data)

Sets the visualization for the current response. Requestly compiles the template as soon as you call set() and shows the result behind the Visualize button. Available in both pre-request and post-response scripts. Parameters:

template (string, required): A Handlebars template. It can contain HTML, <style>, inline event handlers, and <script> tags, including a <script src="..."> that loads a library from a CDN (for example Chart.js).
data (JSON, optional): Any JSON-serializable value. Handlebars expressions such as {{name}} in the template render against it, and rq.getData inside the visualization reads it back at runtime.

Example: render the response as a table

// Post-response script
const template = `
  <style>
    table { width: 100%; border-collapse: collapse; font-family: sans-serif; }
    th, td { border: 1px solid #ddd; padding: 8px; text-align: left; }
    th { background: #f4f4f4; }
  </style>
  <table>
    <tr><th>Name</th><th>Email</th></tr>
    {{#each users}}
      <tr><td>{{name}}</td><td>{{email}}</td></tr>
    {{/each}}
  </table>
`;

rq.visualizer.set(template, { users: rq.response.json() });

Each call to set() replaces the previous visualization. If it runs more than once, including across a pre-request and a post-response script, the last call to run wins.

Viewing the visualization

After a post-response script calls rq.visualizer.set(), a Visualize button appears beside the format selector in the response Body area. Send the request, then click Visualize to switch the body view to your rendered visualization.

A rendered table visualization in the response Body area, with the Visualize button active beside the format selector

Until a script sets a visualization, the Visualize button stays disabled. Hover it to see how to turn it on. When the visualization is showing, two more actions appear beside it:

Refresh re-renders the current visualization without sending the request again. Use it to re-run a chart’s animation or reload the visualization from its captured data.
View Script opens the post-response Scripts tab, where your rq.visualizer.set() call lives.

Switching the format selector back to Raw, Hex, or Base64 returns the body to its normal view.

Reading your data inside the visualization

There are two ways to get your data into the rendered output:

Handlebars expressions. Anything in {{ ... }} renders against the data you passed to set(). This is the simplest path for tables and text.
rq.getData. Call it inside a <script> to read the same data back as a JavaScript object. This is the path for charts and other libraries that build the DOM themselves.

rq.getData takes a callback with the Node-style (error, data) signature:

rq.getData(function (error, data) {
  // `data` is the value you passed to rq.visualizer.set()
  console.log(data);
});

Example: render a chart with Chart.js from a CDN

// Post-response script
const template = `
  <canvas id="chart" width="400" height="200"></canvas>
  <script src="https://cdn.jsdelivr.net/npm/chart.js"></script>
  <script>
    rq.getData(function (error, data) {
      new Chart(document.getElementById("chart"), {
        type: "bar",
        data: {
          labels: data.labels,
          datasets: [{ label: "Requests per day", data: data.values }],
        },
      });
    });
  </script>
`;

rq.visualizer.set(template, {
  labels: ["Mon", "Tue", "Wed"],
  values: [12, 19, 7],
});

rq.visualizer.clear()

Removes the current visualization and returns the Visualize button to its disabled state. Use it to hide a stale visualization when the response does not warrant one. Parameters: none.

// Post-response script
if (rq.response.code !== 200) {
    rq.visualizer.clear();
}

How the visualization is isolated

Your visualization runs in a sandboxed frame that is separated from the rest of Requestly. Inside it you can load scripts from a CDN and use inline event handlers, but the frame cannot read or change the app around it, your cookies, or your other data. If a CDN script fails to load, the failure stays contained in the frame and does not affect Requestly.

When something goes wrong

If your template cannot be compiled (for example a Handlebars syntax error), or your data cannot be turned into JSON (for example it contains a circular reference or a BigInt), Requestly shows a short Template error message in place of the visualization instead of a blank body. A View Script button sits next to the message so you can jump straight to the script and fix it.

Using Postman visualizer scripts

If you import a Postman collection whose scripts call pm.visualizer.set(), Requestly translates them to rq.visualizer.set() automatically, so your visualizations work without editing the script. Inside the visualization, pm.getData works alongside rq.getData, so Postman visualization templates render unchanged.

Getting Started

Mock Server

Collaboration & Projects

Account & Administration

rq.visualizer (Response visualization)

rq.visualizer.set(template, data)

Viewing the visualization

Reading your data inside the visualization

rq.visualizer.clear()

How the visualization is isolated

When something goes wrong

Using Postman visualizer scripts

​rq.visualizer.set(template, data)

​Viewing the visualization

​Reading your data inside the visualization

​rq.visualizer.clear()

​How the visualization is isolated

​When something goes wrong

​Using Postman visualizer scripts

​Related Documentation

rq.visualizer.set(template, data)

Viewing the visualization

Reading your data inside the visualization

rq.visualizer.clear()

How the visualization is isolated

When something goes wrong

Using Postman visualizer scripts

Related Documentation