Skip to main content

Rendered HTML API

developer
GET/v1/domain/render

Loads a public web page in sandboxed Chromium on the EdgeDNS VPS and returns a snapshot of the rendered DOM. Each request uses a fresh browser and context without customer cookies or credentials.

What It Does

Navigates to a public HTTP(S) URL, waits for DOMContentLoaded and an additional 500 milliseconds, then serializes the current DOM. Returns the final URL, document title, observed HTTP status, rendered HTML and VPS measurement provenance. This bounded snapshot does not guarantee that all asynchronous content has finished loading. HTML is limited to 512 KiB. Private destinations are blocked for redirects and subresources; TLS verification stays enabled. One shared browser job runs at a time across staging and production; busy requests return 429 with Retry-After and are not charged. Captures are fresh and uncached.

Why It's Useful

Inspect content generated by JavaScript and compare the rendered page with server HTML. Useful for deployment checks and debugging pages whose content is missing from ordinary HTTP fetches.

Use Cases

Frontend Engineer

JavaScript Content

Check whether the deployed page creates its expected content after JavaScript runs.

Inspect a real DOM snapshot instead of only the initial HTML.

SEO Engineer

Rendered SEO Review

Inspect titles, links and structured data created by client-side code.

Find differences between source HTML and the rendered document without claiming a full crawler simulation.

DevOps Engineer

Deployment Checks

Capture the rendered document from a public deployment URL.

Automate content checks using the same authenticated API as other EdgeDNS diagnostics.

Parameters

NameLocationTypeRequiredDescription
urlquerystringRequiredPublic HTTP(S) URL on port 80 or 443. Bare domains use HTTPS. Credentials and fragments are not accepted.Example: https://example.com/

Response Fields

FieldTypeDescription
htmlstringRendered DOM serialized as HTML; treat it as untrusted page content.
html_bytesnumberUTF-8 size of the returned HTML, at most 524288 bytes.
titlestringObserved document title, limited to 4096 characters.
final_urlstringURL observed after navigation and redirects.
statusnumberObserved HTTP status. An HTTP error page can still produce a DOM snapshot.
captureobjectDOMContentLoaded plus a 500 ms settling interval.
measurementobjectVPS source, request environment, shared runtime, exact release and observation time.

Code Examples

Replace YOUR_API_KEY with your API key. This endpoint requires the developer plan or higher; see plans and usage limits.

cURL
curl --request GET 'https://api.edgedns.dev/v1/domain/render?url=https%3A%2F%2Fexample.com%2F' \
  --header "Authorization: Bearer YOUR_API_KEY"
JavaScript
const response = await fetch(
  "https://api.edgedns.dev/v1/domain/render?url=https%3A%2F%2Fexample.com%2F",
  {
    "method": "GET",
    "headers": {
      "Authorization": "Bearer YOUR_API_KEY"
    }
  }
);

if (!response.ok) {
  throw new Error(`EdgeDNS returned HTTP ${response.status}`);
}
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    'GET',
    "https://api.edgedns.dev/v1/domain/render?url=https%3A%2F%2Fexample.com%2F",
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    timeout=60,
)
response.raise_for_status()
data = response.json()
print(data)

Read the full Rendered HTML guide

Learn the concepts, choose a practical workflow, and interpret the observations from Rendered HTML before acting on them. Run supported checks via MCP or through REST.

Read the guide →

    Related Endpoints

    External References

    Learn more about the standards and protocols behind this endpoint.

    Try This Endpoint

    Test the Rendered HTML endpoint live in the playground.

    Rendered HTML API Reference | EdgeDNS