Authentication

Every request needs an API key. Create one on the API Keys page — the secret key (sk_live_…) is shown once, so store it securely.

API keys

Send your secret key any of these three ways (server-to-server):

  • X-API-Key: sk_live_… header (recommended)
  • Authorization: Bearer sk_live_…
  • ?access_key=sk_live_… query parameter
Header auth
curl https://screenshotforweb.com/api/v1/usage -H "X-API-Key: sk_live_your_key"

Using keys in a browser

Never ship your secret key to the client. To render screenshots in a browser, use a signed request instead — you expose only a public access key and a per-request signature.

Dashboard sessions

First-party dashboard requests use a short-lived session JWT (Authorization: Bearer) rather than an API key — you don't need to handle this unless you're building against the dashboard directly.