HEAD requests

Render screenshots with HEAD requests without downloading them. They count towards your quota like GET.

Changelog1 min read

Written by

Dmytro Krasun

Published on

The API now supports HEAD requests. They take the same options as GET and return the same status and headers, without the file. Previously, HEAD requests failed with a validation error.

HEAD requests that render count towards your quota, just like GET, even though you don’t receive the file. Without cache=true, every HEAD request renders again and counts. If link checkers, crawlers or uptime monitors send HEAD requests to your API URLs, turn on caching or point them elsewhere.

With cache=true, a HEAD request renders ahead of time: a later GET with the same options is served from the cache and doesn’t count towards your quota.

See HEAD requests.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Added support of external identifiers

Added support of external identifiers

Check out how to use the external identifier to improve tracking of webhook executions.

Read more

1 min read

Fail if there is nothing to click on

Fail if there is nothing to click on

A new option has been added to fail or not to fail the screenshot rendering if there is nothing to click on.

Read more

1 min read

Fewer failed requests

Fewer failed requests

Requests that reach a busy rendering server are retried on another one, HTML and markdown of pages that redirect themselves no longer fail, and storage errors say what to fix.

Read more

1 min read

Automate website screenshots

Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.