Check live service health and documented failure responses before you integrate.
Web Data
Website screenshot API
Capture any public web page with one request. Choose desktop or mobile, the visible area or the full page, and PNG, JPEG, WebP or PDF. Get the file as base64 in JSON or download it directly.
Used by people at these companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Send your API key with the documented header and keep requests consistent across services.
Start from the curl and HTTP samples, then map the parameters into your application code.
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
Example response
HTTP status codes
Endpoints
/v1/screenshot
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Pages are loaded in an isolated browser with JavaScript, styles, fonts and images, just like a visitor sees them.
Capture a 1366 px desktop view or a 390 px mobile view with touch and mobile layout.
Capture the visible area or scroll the whole page, up to 8,000 px high.
Get base64 data with dimensions and size in JSON, or set output=binary to receive the image or PDF directly.
Example request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/screenshot?url=example.com&device=mobile&full_page=true"
Example response
{
"status": "ok",
"final_url": "https://example.com/",
"http_status": 200,
"capture": {
"format": "png",
"mime_type": "image/png",
"device": "mobile",
"full_page": true,
"width": 390,
"height": 2480,
"bytes": 412870,
"data_base64": "iVBORw0KGgoAAAANSUhEUgAA..."
}
}
Frequently asked questions
PNG, JPEG and WebP images, and A4 PDF documents with backgrounds.
No. Pages are captured as an anonymous visitor sees them on first load, without clicking, typing or accepting cookie banners.
Full-page captures stop at 8,000 px. Captures larger than 5 MB return status unknown and are refunded.
10 credits per capture. Blocked or failed pages are refunded.
Related tools and resources
HTTP status codes
These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
Request successful
Invalid parameters
Missing or invalid API key/session.
Not enough credits to run this request.
Rate limit exceeded
Capture a screenshot

