Better validation error messages

ScreenshotOne now returns better validation error messages and no longer exposes unnecessary validation details.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

We improved request validation errors across the ScreenshotOne API.

When a request is not valid, the API now includes the reason directly in the error_message field, for example: The request is not valid: "full_page_scroll" is not allowed.

We also removed the old error_details response field from validation errors. It exposed low-level validation details that most integrations did not use, while making responses noisier than necessary.

The result is a smaller error response with a better message about which option does not work and why.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Chrome/Chromium upgraded to the latest version

Chrome/Chromium upgraded to the latest version

ScreenshotOne now renders pages with the latest stable Chrome/Chromium release for up-to-date web platform support and rendering behavior.

Read more

1 min read

Better Markdown output

Better Markdown output

Markdown output is now cleaner by removing non-content HTML blocks during conversion.

Read more

1 min read

Better error coverage and documentation

Better error coverage and documentation

Since a few months ago, it has been possible to check errors in the dashboard request log and get explanations and more details in the documentation. But!

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.