Screenshot API
documentation

Turn a website URL into an image, PDF, or scrolling video with one HTTP request. Start with a working example, then make the capture your own.

Make your first request API reference

GET & POSTPNG · JPEG · WebPPDF · WebM

From URL to file

Your first capture

01Create an API key in your dashboard.
02Set SCREENSHOTENGINE_API_KEY in your shell environment.
03Run the request and open screenshot.png.

HTTP 200 returns the file bytes directly. Errors return JSON. No job polling needed.

Node.js, Python & PHP examples

cURL · full-page screenshot

curl --fail-with-body --request POST 'https://api.screenshotengine.com/v1/screenshot' \
  --header "Authorization: Bearer $SCREENSHOTENGINE_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "https://example.com",
  "format": "png",
  "height": "full"
}' \
  --output screenshot.png

Build your integration

The details you need, from authentication to production.

Authentication

Authenticate ScreenshotEngine GET and POST requests, store API keys securely, and understand the difference between query and Bearer authentication.

API parameters

Compare GET and POST options for screenshots, PDF, WebM video, viewport sizes, CSS selectors, delays, watermarking, and cache control.

Code examples

Copy server-side ScreenshotEngine examples for Node.js, Python, PHP, and cURL, with API key environment variables and binary file handling.

Capture recipes

Practical ScreenshotEngine requests for full-page and mobile screenshots, CSS elements, dark mode, cookie banners, PDF, WebM video, and watermarks.

Caching & freshness

Understand ScreenshotEngine cache behavior, X-Cache response headers, successful-request usage, and the POST no-cache option for fresh screenshots.

Errors & rate limits

Resolve ScreenshotEngine HTTP 400, 401, 429, 500, and 503 errors. Understand monthly quotas, retry behavior, blank captures, and output files.

Works with your tools

Explore the API interactively, connect an AI agent with MCP, or add screenshots to an automation. Use the Markdown documentation when working with an AI coding assistant.

API explorer →MCP setup →n8n guide →viaSocket guide →Full docs for AI →