USE CASE · URL → PDF
URL to PDF API
Point PDFRelay at a live page instead of raw markup. Pass a public URL and get back the same document a visitor would see, rendered by real headless Chromium, with no template to maintain separately from the page itself.
How URL mode works
POST /api/v1/pdf accepts a url field in place of html, exactly one of the two per request. The target must be a public http(s) address: private and internal addresses are blocked by an SSRF guard before the fetch happens, so the endpoint can’t be used to reach your internal network.
The waitUntil option controls when the page counts as ready (load, domcontentloaded, or networkidle), so pages that finish rendering after the initial load event still come out complete. A navigation that fails to load returns a 502 with a navigation_failed error code instead of a silent blank PDF.
Where URL mode fits
| Scenario | Why URL mode |
|---|---|
| Reports and dashboards | Export a live authenticated or public page as-is, no re-implementation as a template. |
| Public content snapshots | Archive a page exactly as Chromium renders it, CSS and fonts included. |
| Untrusted or user-supplied links | SSRF guard blocks private and internal addresses before fetching. |
| Repeat exports | Identical URL and options are served from a short-TTL cache, free of quota. |
TRY IT · FREE · NO SIGNUP
Render a live URL now
Try the free playground against your own HTML first, then switch to URL mode in your integration using the same options.
Free tier: 150 documents/month, no card. See FAQ for common questions, or compare rendering engines in PDFRelay vs SelectPdf. Back to the PDFRelay homepage.