Web Page Screenshot Capture

Urlbox renders any URL into a precise screenshot on request. A Beam agent sends approved URLs, reads the returned image, and stores it where your workflow expects, generating shots at the sizes and formats your rules define. If a page fails to load, times out, or returns an error state, the agent retries within limits and then hands the failure to a person instead of saving a blank image. Each capture is recorded against its source URL, so previews and archives stay current without a developer running the API by hand every time.

PDF Rendering

Urlbox can output a full page as a PDF as well as an image. A Beam agent reads which pages need archiving, requests the PDF under your format rules, and files it where records are kept, naming each by source and date. Pages behind logins or returning partial content are set aside for a person to review rather than stored incomplete. The agent logs every rendered document, so contracts, invoices, or web receipts are captured consistently, and anything the connector and account permissions cannot reach is escalated to a human for a decision.

Rendering Failure Handling

Screenshot and PDF jobs sometimes fail on slow, blocked, or broken pages. A Beam agent reads each job's result, and when one errors, applies your rules: retry a set number of times, adjust wait settings, then, if it still fails, notify the owner with the URL and error. Persistent failures across many pages are grouped and routed to an engineer to investigate a wider issue. The agent records every attempt and outcome, so capture pipelines stay reliable and people only step in when automatic recovery genuinely cannot finish the job.