Swap the html field for a url field
The endpoint and the options are identical. Everything you can do with raw HTML you can do with a live URL, which makes it trivial to migrate an existing integration.
curl -X POST https://api.filecook.com/render/pdf \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/reports/q3",
"options": { "format": "A4", "waitFor": "networkidle" }
}' -o report.pdf
JavaScript-heavy pages, handled
Single-page apps do not finish rendering when the document loads — they finish when the last request settles. Filecook lets you say exactly what "ready" means for your page instead of guessing with a fixed sleep.
waitFor: "networkidle"— capture once network traffic goes quietwaitFor: "#report-ready"— wait for a specific element to appearwaitFor: 2000— a plain millisecond delay when you need the blunt instrumentemulateMedia: "screen"— capture the on-screen layout rather than the print stylesheet
Pages behind a login
Dashboards worth exporting are usually gated. Pass custom request headers, cookies, or an HTTP basic auth pair and the renderer will authenticate before it captures. Combine that with origin whitelisting so only your own domains can be rendered with your key.
