Skip to main content
SaaS|Frontend Developer / QA Engineer

JavaScript Rendering & Deployment Checks

Capture rendered HTML and screenshots from a public deployment

Capture rendered HTML and screenshots from a public deployment. Follow the request examples below and review the observation limits before adding the workflow to your release or audit process.

Implementation example by the EdgeDNS team · Updated

The Challenge

A successful HTTP response can still display an error page or omit content created by JavaScript.

The Workflow

Call render and screenshot sequentially for a public deployment URL. Inspect the rendered DOM, observed status, final URL, and screenshot. Each call uses a fresh unauthenticated Chromium context, waits for DOMContentLoaded plus 500 ms, and captures a bounded observation. The screenshot is a 1280×720 viewport JPEG; it is not a full-page visual regression test. Developer access is required. Capacity-limited 429 responses include Retry-After and are uncharged.

Endpoints Used

Combine these EdgeDNS endpoints to build this solution.

GET
/v1/domain/renderAPI reference

Rendered HTML: Get HTML after JavaScript executes in Chromium

GET
/v1/domain/screenshotAPI reference

Page Screenshot: Capture a web page as a JPEG screenshot

What this workflow helps you do

Inspect JavaScript-created content

Review the returned DOM instead of relying only on source HTML.

Retain visual evidence

Decode screenshot.base64 and save the JPEG in your own review artifacts.

Interpret the capture scope

No customer cookies or credentials are carried into the browser; asynchronous content may still be loading.

Code Example

Capture rendered HTML and screenshots from a public deployment

javascript
const headers = { Authorization: 'Bearer YOUR_API_KEY' };
const checks = [
  {
    "path": "/v1/domain/render",
    "params": {
      "url": "https://example.com/"
    }
  },
  {
    "path": "/v1/domain/screenshot",
    "params": {
      "url": "https://example.com/"
    }
  }
];

// Run sequentially to keep concurrency bounded. API tier restrictions apply.
for (const { path, params } of checks) {
  const url = new URL(path, 'https://api.edgedns.dev');
  url.search = new URLSearchParams(params).toString();
  const response = await fetch(url, { headers });
  const result = await response.json();
  if (!response.ok) {
    throw new Error(`${path}: ${response.status} ${result.error?.message ?? 'Request failed'}`);
  }
  // Keep the response metadata and any partial/unknown findings for review.
  console.log(path, result);
}

Learn More

Explore industry standards and best practices related to this use case.

Ready to build JavaScript Rendering & Deployment Checks?

Get started with 200 free API requests per month. No credit card required.

Other Use Cases

JavaScript Rendering & Deployment Checks | EdgeDNS