Website to PDF is a simple tool for converting a website to PDF. It returns the PDF file generated from the website.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Website to PDF response payload
}
}
About the Website to PDF API
Website to PDF works by converting the website provided into a PDF file. It uses advanced algorithms to convert the website into a PDF file and returns the PDF file.
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
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Website to PDF
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Website to PDF API do?
How do I authenticate Website to PDF API requests?
How much does the Website to PDF API cost?
How fast is the Website to PDF API?
What response formats does the Website to PDF API support?
What HTTP method does the Website to PDF API use?
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
| Parameter | Type | Example | Description |
|---|---|---|---|
urlRequired | string | https://en.wikipedia.org/wiki/PDF | The URL of the website to convert to PDF url |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
marginTopOptionalPremium | number | The top margin of the PDF in inches (e.g., 0.4) default 0.4 | |
marginRightOptionalPremium | number | The right margin of the PDF in inches (e.g., 0.4) default 0.4 | |
marginBottomOptionalPremium | number | The bottom margin of the PDF in inches (e.g., 0.4) default 0.4 | |
marginLeftOptionalPremium | number | The left margin of the PDF in inches (e.g., 0.4) default 0.4 | |
landscapeOptionalPremium | boolean | Set to true for landscape orientation default false |
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}'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.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
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.
{
"status": "ok",
"error": null,
"data": {
"marginLeft": "0.4in",
"marginRight": "0.4in",
"marginTop": "0.4in",
"marginBottom": "0.4in",
"landscape": false,
"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.
| Field | Type | Example | Description |
|---|---|---|---|
marginLeft | string | "0.4in" | Left margin of generated PDF in inches |
marginRight | string | "0.4in" | Right margin of generated PDF in inches |
marginTop | string | "0.4in" | Top margin of generated PDF in inches |
marginBottom | string | "0.4in" | Bottom margin of generated PDF in inches |
landscape | boolean | false | PDF orientation mode (true for landscape) |
pdfName | string | "128deceb-c515-444b-8863-82cb3f6ba632.pdf" | Generated PDF filename with unique identifier |
expires | number | 1766097122116 | PDF expiration timestamp in milliseconds |
url | string | "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts" | Original source URL that was converted to PDF |
downloadURL | string | "https://storage.googleapis.com/apiverve-helpers.appspot.com/websitetopdf/128deceb-c515-444b-8863-82cb3f6ba632.pdf?GoogleAccessId=1089020767… | Temporary signed URL for downloading the PDF file |
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.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
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.
| Plan | Per month | Credits | Website to PDF calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 5 | Free |
| Starter | $29.99 | 200,000 | 5,000 | $6.00 |
| Pro | $99.99 | 1,000,000 | 25,000 | $4.00 |
| Mega | $299.99 | 4,000,000 | 100,000 | $3.00 |
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.
Call it from cURL — POST /v1/websitetopdf
No SDK to install — this is a plain HTTPS call to /v1/websitetopdf with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/websitetopdf" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/websitetopdf
Install the Node.js SDK, then call the Website to PDF API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/websitetopdfconst res = await fetch("https://api.apiverve.com/v1/websitetopdf", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/websitetopdf
Install the Python SDK, then call the Website to PDF API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-websitetopdfimport requests
res = requests.get(
"https://api.apiverve.com/v1/websitetopdf",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/websitetopdf
Install the C# / .NET SDK, then call the Website to PDF API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.WebsitetoPDFusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/websitetopdf");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/websitetopdf
No SDK to install — this is a plain HTTPS call to /v1/websitetopdf with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/websitetopdf", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/websitetopdf
No SDK to install — this is a plain HTTPS call to /v1/websitetopdf with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/websitetopdf");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/websitetopdf
No SDK to install — this is a plain HTTPS call to /v1/websitetopdf with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/websitetopdf")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
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.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Website to PDF API.
Documents
- HTML to PDF
- Invoice Generator
- Website to PDF
Related articles
All articles →
Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read 
PDF Generation API: Invoices, Reports, DocumentsGenerate PDFs from HTML or Markdown. Perfect for invoices, receipts, reports, and any document you need to create programmatically.Read 
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read