Authentication

ScreenshotAPI authenticates requests via API keys. Pass your key as a Bearer token or as the access_key query parameter.

Every request must include a valid API key. Find yours in the Dashboard → API Keys<\/strong> section.<\/p>

Option 1: Authorization header (recommended)<\/h3>
Pass your key as a Bearer token in the Authorization<\/code> header. This keeps the key out of server logs and browser history.<\/p>
Authorization: Bearer YOUR_API_KEY<\/code><\/pre>Option 2: Query parameter<\/h3>Append access_key=YOUR_API_KEY<\/code> to the request URL. Convenient for quick testing but avoid in production as keys can appear in logs.<\/p> https:\/\/screenshotcore.com\/api\/v1\/screenshot?access_key=YOUR_KEY&url=https:\/\/example.com<\/code><\/pre>Note:<\/strong> The API key must be in the header or query string — passing it inside a JSON or form body is not supported. All other capture parameters can be passed in any format.<\/p> Requests with a missing or invalid key receive 401 Unauthorized<\/code>.<\/p>

`Code Examples`

# Option 1: Bearer token header (recommended)
curl "https://screenshotcore.com/api/v1/screenshot?url=https://example.com" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --output screenshot.png

# Option 2: Query parameter
curl "https://screenshotcore.com/api/v1/screenshot?access_key=YOUR_API_KEY&url=https://example.com" \
  --output screenshot.png

`Response`

(Raw bytes, Content-Type: image/png. Headers: X-Response-Time, X-Cache, X-Request-Id)

Your First CaptureCapture a website as an image