# Try a real render in Run

Run a template with an API key, version, variant, and data in the Run.

**Run** lets you supply data and create PDFs inside the editor. Select the template edition, fill in its inputs, and inspect the result in one place before connecting the template to your software.

## 1. Select a key, version, and variant

Save and publish the intended version, then open **Run**. Select a project API key with `template:render`, a **Version**, and a **Variant** name. Create a key in [API Keys](/docs/developers/keys/) if needed.

Run’s selectors are independent of the open editor view. You can run v1 while viewing v2. Changing Version loads that saved version’s Parameters, Defaults, and Variants; wait for it to load before entering data. Inputs are kept separately for each template version in this browser. Draft versions can be selected, but must be published before rendering.

<figure class="doc-sim data-assets-illustration workflow-illustration" aria-label="Run → API key → Version → Variant">
<div class="sim-stage"><div class="sim-panel"><div class="ds-head"><strong>RUN</strong><div class="wf-actions"></div></div><div class="wf-fields"><div><small class="sim-label">API KEY</small><span class="sim-input wf-select sim-focus">Project key<svg class="sim-chevron" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true"><path d="m4 6 4 4 4-4" /></svg></span></div><div><small class="sim-label">VERSION</small><span class="sim-input wf-select">v2<svg class="sim-chevron" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true"><path d="m4 6 4 4 4-4" /></svg></span></div><div><small class="sim-label">VARIANT</small><span class="sim-input wf-select">Standard<svg class="sim-chevron" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true"><path d="m4 6 4 4 4-4" /></svg></span></div></div></div></div>
<figcaption>Run → API key → Version → Variant</figcaption>
</figure>

## 2. Fill in the job’s Parameters

Expand Parameters in Run and edit the test values. Fields come from the declared schema; objects and arrays still need their correct types.

These inputs belong to the PDF job and do not change the template’s Defaults. Resetting inputs restores the default Parameter values.

<figure class="doc-sim data-assets-illustration workflow-illustration" aria-label="Run inputs belong to the job and do not replace Defaults">
<div class="sim-stage"><div class="sim-panel"><div class="ds-head"><strong>RUN · Parameters</strong><div class="wf-actions"></div></div><div class="wf-fields"><div><small class="sim-label">recipient</small><span class="sim-input sim-focus">Tembuilder</span></div><div><small class="sim-label">copies</small><span class="sim-input">2</span></div></div><div class="ds-code"><code>{ &quot;recipient&quot;: &quot;Tembuilder&quot;, &quot;copies&quot;: 2 }</code></div></div></div>
<figcaption>Run inputs belong to the job and do not replace Defaults</figcaption>
</figure>

## 3. Generate a PDF and open the result

Choose **Render**. The job appears in Run’s history while processing. Open its result row to view status and download the PDF on success.

Run performs real rendering: successful jobs count toward quota and produce retained output. Use editor [preview](/docs/renders/preview-render/) while adjusting the layout.

For a failed job, open its error details to identify whether the input, template, or usage conditions need attention before retrying.

<figure class="doc-sim data-assets-illustration workflow-illustration" aria-label="Render → history → open the result → Download">
<div class="sim-stage"><div class="sim-panel"><div class="ds-head"><strong>Render · #a18f</strong><div class="wf-actions"></div></div><div class="wf-rows"><div class=""><span>Status</span><small>Success</small></div><div class=""><span>Version</span><small>2 · Standard</small></div></div><div class="wf-output"><span>document.pdf</span><span class="sim-control sim-focus">↓ Download</span></div></div></div>
<figcaption>Render → history → open the result → Download</figcaption>
</figure>

## 4. Copy a request to start integrating

Run’s copy menu offers **cURL**, **JavaScript**, and **Python**. Snippets use `<YOUR_API_KEY>`; supply the key in your own execution environment.

The snippet uses the version, variant, and input values currently selected in Run. Copy it after choosing the combination you intend to integrate; changing the form afterwards does not change a snippet already copied. For request fields, status, and download endpoints, see [Render API reference](/docs/developers/render-reference/).

<figure class="doc-sim data-assets-illustration workflow-illustration" aria-label="Copy → cURL / JavaScript / Python">
<div class="sim-stage"><div class="sim-panel"><div class="ds-head"><strong>RUN</strong><div class="wf-actions"><span class="sim-control">Copy ⌄</span></div></div><div class="wf-rows"><div class="sim-focus"><span>Copy cURL</span><small>curl</small></div><div class=""><span>Copy JavaScript</span><small>fetch</small></div><div class=""><span>Copy Python</span><small>requests</small></div></div></div></div>
<figcaption>Copy → cURL / JavaScript / Python</figcaption>
</figure>
