Skip to main content
scrnshot is a screenshot API: send a URL and a few options, get back a hosted image. No headless browser to manage, no infrastructure to run.

​
Base URL

All API requests go to:
The dashboard, where you create an account and manage API keys, is at scrnshot.site.

​
How the API is organized

Capture

POST /v1/screenshots — the endpoint you’ll use for almost everything.

Usage

GET /v1/usage — check quota consumption programmatically.

Authentication

API keys, headers, and how revocation works.

Plans & limits

What each plan allows, and what happens when you hit a limit.
Two endpoints are not part of the programmatic API even though they live under the same domain:
  • POST /demo/screenshot — powers the live demo on scrnshot.site. It’s unauthenticated and IP-rate-limited to 5 requests/day. Don’t integrate against it.
  • /v1/keys and /v1/billing/* — dashboard-only endpoints authenticated with a session cookie, not an API key. They’re documented in the API reference for completeness, not because you’ll call them from server code.

​
Next steps

Head to Quickstart to create an API key and capture your first screenshot.