Website to PDF API

About the Website to PDF API

A website to PDF API and webpage to PDF converter: pass a public URL and the page is rendered into a PDF file, in A4 or, on paid plans, Letter, Legal or another paper size. The page is loaded in headless Chrome and printed to PDF, so you get the same kind of document as saving a page from the browser, without running a browser yourself.

The response returns a temporary download link rather than the file itself, valid for two days, along with the generated file name, the URL that was converted and the margins and orientation used. It is a fit for archiving web pages, saving receipts and order confirmations, attaching a report page to an email, or keeping a dated copy of a page for records.

The Free plan prints in A4 portrait with 0.4-inch margins, with background colors and images included. Paid plans add control over the layout: custom margins on each side, landscape orientation, eight paper sizes from A6 up to Tabloid and Ledger, and an option to turn off background printing for an ink-saving document. Paid plans also receive the page count of the finished PDF.

How it works

The URL is first checked to be a public web address; private, loopback and other internal hosts are refused. The page is then loaded by a headless Chrome rendering service and printed with Chrome's PDF output. The render has a 25-second limit, and failures such as an unreachable site or a timeout come back as an error response with an explanatory message.

Margins are numbers in inches and default to 0.4 on every side; the response echoes them as strings with an in suffix, such as "0.4in". landscape defaults to false. format is matched case-insensitively against A4, Letter, Legal, Tabloid, Ledger, A3, A5 and A6, and anything else falls back to A4. printBackground defaults to true; set it to false and the page's background colors and images are left out.

After rendering, the PDF is opened once to count its pages. If that read fails, the file is still delivered and pageCount is null. The PDF is stored under a random pdfName, and downloadURL is a signed link that works until expires, a Unix timestamp in milliseconds two days after the call. The response never contains the PDF bytes, so download the file before it expires.

On the Free plan the margin, landscape, format and printBackground parameters are removed before rendering, so every free PDF uses the defaults, and the format and pageCount response fields are null. Pages behind a login, cookie wall or bot check render as whatever the browser is shown, which may be the wall itself.

What people use it for

Billing Receipt Archival

SaaS platforms pass payment confirmation URLs to provide customers with downloadable PDF receipts via the temporary download link.

Article Offline Reading

To preserve online research, bookmarking tools submit article URLs and save the resulting PDF download links for offline reading.

Policy Compliance Tracking

When terms of service update, legal teams generate timestamped PDF records directly from live policy pages for compliance archives.

Automated Report Exports

Archive public analytics dashboards by converting page URLs into PDF files to attach to scheduled client reports.

Without writing code

WebPage to PDF for Windows saves a whole list of pages as PDFs in one press.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — POST /v1/websitetopdf

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Optional

1
2
3
4

curl -X POST "https://api.apiverve.com/v1/websitetopdf" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts","marginTop":0.4,"marginRight":0.4,"marginBottom":0.4,"marginLeft":0.4,"landscape":false,"format":"value","printBackground":true}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — POST /v1/websitetopdf

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

{
  "status": "ok",
  "error": null,
  "data": {
    "marginLeft": "0.4in",
    "marginRight": "0.4in",
    "marginTop": "0.4in",
    "marginBottom": "0.4in",
    "landscape": false,
    "format": "A4",
    "pageCount": 6,
    "pdfName": "128deceb-c515-444b-8863-82cb3f6ba632.pdf",
    "expires": 1766097122116,
    "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts",
    "downloadURL": "https://storage.googleapis.com/apiverve-helpers.appspot.com/websitetopdf/128deceb-c515-444b-8863-82cb3f6ba632.pdf?GoogleAccessId=1089020767582-compute%40developer.gserviceaccount.com&Expires=1766097122&Signature=LI747FKqKj5i5TYX3KIoVy%2FHgXsLOSXfVEUM0Ekqz2SiiYOZWuk3Of7QBDUklSrcbjiHV0AjbzFTKt6oDU83UkN282HbmhxwrolN6v1Zb9twVi1y7gmTpapCiJi%2BpA1r89ioe%2Fe0%2FV7KrIWaqsorzpdJrnMqe2izMWBaZq%2FYkSO2qlwSyhg2R8EsfxYNAANtd%2FuNS0RuIzqTdhNCiTrRirnDAKS3dMCySQJRznHFnyqzNj1OXwVjvdpSMn9XhWCUa%2FDRR8q%2BE9B0yF8eTvIrDSe2OzJT%2FJLc9rxcLfXAny21gtNqrzMJPU4yM9Ge%2BEbepmDnNZf9xpODNsnq5eLF0g%3D%3D"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 40 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Website to PDF form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Website to PDF API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1