Marketing claims, terms-of-service versions, competitor promotions, regulated disclosures — teams increasingly need to prove what a page said at a point in time. Manual screenshots don't scale and skip pages; browser print-to-PDF mangles layouts.
An API capture renders the page in real Chrome, returns a full-page PNG or PDF, and slots into whatever schedule and storage your compliance process requires. Capture timestamps come back in the response for your audit log.
import requests, datetimeresponse = requests.post("https://api.screenshotty.link/api/v1/screenshot",json={"url": "https://example.com/terms","format": "application/pdf","full_page": True,"ready_event": "networkidle",},headers={"X-Api-Key": "YOUR_API_KEY"},)stamp = datetime.datetime.now(datetime.timezone.utc).strftime("%Y%m%dT%H%M%SZ")with open(f"archive/terms-{stamp}.pdf", "wb") as f:f.write(response.content)
Capture the entire page in the format your records system expects, ads stripped or kept as needed.
Drive captures from cron for recurring archives or from your app when a record-worthy event fires.
Capture per-country variants of localized pages with the country parameter.
Cookies and custom headers let you archive logged-in or gated content.
That depends on jurisdiction and context — consult counsel. What the API provides is the technical foundation: an automated, repeatable capture process with consistent rendering and timestamps you record alongside each capture in your own audit log.
PDF for document-style records workflows (it paginates and prints predictably); full-page PNG when you want a single image exactly matching the rendered page. Many teams store both from the same request schedule.
Yes. 100 screenshots per month free, no credit card required. Paid plans start at $9/month for 2,500 screenshots with $0.004 pay-as-you-go overage.
Submit captures concurrently with webhook_url set; your handler receives each result and writes it to your storage (S3, GCS, or your DMS) with the metadata your retention policy needs.