URL to PDF Render API

When to use this API

This API captures a target URL and generates a PDF representation of the rendered page. It is built for automated evidence collection, reporting and document workflows where web content must be stored as a PDF artifact.

• You need to archive dynamic web content as a document.
• You want periodic snapshots of web pages for compliance or records.
• You need reproducible page captures in backend processes.

Typical use cases

• Compliance evidence archiving.
• Client-ready snapshots of dashboards or reports.
• Operational capture of partner or public pages.

Billing model

URL to PDF billing is based on generated PDF pages. One generated PDF page equals one pdf_page service billing event; it is not billed as a generic API call.

• More generated PDF pages means more pdf_page billing events.
• Validation failures, blocked URLs and render failures are not treated as generated-page events.
• Target page layout, page size, margins, wait strategy and loaded content can affect generated page count.

APIRAPTOR token model

Tokens are APIRAPTOR's communication unit. One token equals 100 subtokens, and service usage is charged per service billing event.

• Trial availability, token amount and duration come from Billing configuration.
• Users have access to all services from day one; services are not premium-gated per plan.
• URL to PDF uses the pdf_page service billing event for generated PDF pages.

Public-page rendering boundary

URL to PDF renders publicly reachable HTTP/HTTPS pages only. It respects third-party access controls and does not bypass logins, paywalls, robots restrictions, anti-bot protections or other access controls.

• Loopback, private, link-local and internal-only network targets are blocked by URL safety rules.
• Pages that require authentication, special browser state or blocked resources may fail or produce incomplete output.
• Use the service for content you are allowed to access and render.