Screenshot API methods

Choose the right request for every screenshot.

Use GET for direct, single-page captures and signed image embeds. Use POST when your workflow needs structured data, bulk URLs, storage, or automation.

View request examplesCompare methods
  • Same capture endpoint
  • 3 regions
  • No concurrency throttling
api.addscreenshots.com
GET
Direct captureURL + query parameters
Image
POST
Automated workflowURL + JSON payload
Job
Shared endpoint/screenshotsAvailable
Make the choice

Match the HTTP method to the job.

Both methods use the same capture engine. The main difference is how much request data you need to send and how the result will be used.

GET

Best for direct captures

Keep simple, immediate screenshots easy to test, embed, and share.

  • One URL per request
  • Minimal parameters
  • Signed public embeds
  • Dashboard and CMS previews
See the GET example
POST

Best for structured workflows

Use a JSON body when requests grow beyond a compact query string.

  • Bulk URLs and sitemaps
  • Storage templates
  • Metadata and comparisons
  • Automated capture jobs
See the POST example
Use caseRecommendedWhy
Single screenshot with minimal parametersGETA simple, cacheable URL for image tags, testing, and signed hotlinks.
Bulk URLs, sitemaps, or entire domainsPOSTA JSON payload avoids query-string limits and supports asynchronous jobs.
Screenshots embedded on public pagesGETWorks with tokens created using API key signatures.
Storage templates, metadata, or change detectionPOSTSend fields such as storageid, metadata, compare, and webhook.
Working requests

Send options in the query string or JSON body.

Both examples request the same JPEG full-page capture at 80% quality. Replace the API key and target URL before sending the request.

GET

Query-string request

Place the target url last so its own query variables cannot conflict with capture parameters.

// Line breaks added for readability
GET https://api.addscreenshots.com/screenshots
?apikey=YOUR_API_KEY
&quality=80
&format=jpeg
&fullpage=true
&url=https://example.com
POST

JSON-body request

Parameters can be supplied in the query string and/or an application/json body.

POST https://api.addscreenshots.com/screenshots
?apikey=YOUR_API_KEY&quality=80

{
  "url": "https://example.com",
  "format": "jpeg",
  "fullpage": true
}

The API behavior is consistent. Options such as image quality, output format, and full-page capture work with either method.

One capture platform

Keep the same capabilities as workflows grow.

Start with a direct GET request, then move to POST without changing the screenshot engine or destination options.

Page control

Inject custom CSS or JavaScript and emulate the device needed for the capture.

Regional capture

Run screenshots from the US, Europe, or Australia and Asia Pacific.

Direct delivery

Store results in S3, Azure, GCP, Cloudflare R2, FTP, or webhook destinations.

Ready for automation

Build a capture pipeline without maintaining browser workers.

Combine POST requests with storage templates, scheduled jobs, visual comparisons, and webhooks for repeatable monitoring at scale.

Review pricingSecure your API keys