How to Render a execute/html Response in Postman

Use Postman Visualizer to display the generated Quik! HTML form instead of an escaped JSON string.

Applies to

Quik! Forms Engine requests that call POST /rest/QuikFormsEngine/qfe/execute/html and return generated HTML in ResultData.HTML.


Overview

The execute/html endpoint returns the generated form HTML inside a JSON response. Because the HTML is encoded as a JSON string, copying the value directly into a browser may display escaped text instead of a usable form viewer.

Postman Visualizer can render the HTML directly in the Postman response area so you can inspect the generated form, confirm field values, and compare the output with your request payload.

Before you begin

  • Confirm the request completes successfully and returns a JSON response.
  • Confirm the response includes ResultData.HTML.
  • Use a test or non-production environment whenever possible.
  • Remove or mask sensitive customer data before saving or sharing examples.

Add the Visualizer script

  1. Open the execute/html request in Postman.
  2. Open Scripts, then select Post-response.
  3. Add the following script:
const json = pm.response.json();
pm.visualizer.set(`{{{html}}}`, {
  html: json.ResultData.HTML
});

Postman should display the generated Quik! HTML form viewer instead of the escaped JSON value.

How to use the rendered form

  • Confirm the expected forms are included.
  • Compare displayed field values with the FormFields values in your request.
  • Check form-group instances and instance suffixes when your package includes more than one group.
  • Determine whether the reported behavior is already visible in the HTML output or appears later in PDF or e-sign processing.

Troubleshooting

Problem

What to check

Problem

What to check

The Visualize tab is blank

Confirm the response includes ResultData.HTML and that the response body is valid JSON.

HTML is returned at a different path

Update the script to use the property that contains the HTML. For example, use json.HTML if HTML is at the response root.

The request returns 401 Unauthorized

Confirm the Bearer token is valid, the token variable is populated, and the intended Postman environment is active.

The form renders, but Save, Print, Submit, or Sign does not work

Some actions depend on callback URLs, sign URLs, hosted resources, or environment-specific settings. Rendering is still useful for visual prefill validation.

The output shows escaped characters

Make sure you are reviewing the Visualize tab, not copying the encoded JSON string into a browser.


Safe testing practices

Protect customer data

Do not store passwords, access tokens, Social Security numbers, account numbers, or other sensitive values in shared Postman collections, screenshots, or documentation.

  • Avoid creating production e-sign envelopes unless the test is approved and required.
  • Use sanitized payloads when sharing examples with Quik! Support.
  • Record whether the issue appears in HTML preview, generated PDF, or the final e-sign envelope.