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
Get favicon used by a website with ScreenshotOne API

Get favicon used by a website with ScreenshotOne API

Now you can get favicon used by a website with ScreenshotOne API in just one simple API call.

Read more

1 min read

ScreenshotOne can now return screenshots and HTML in one request

ScreenshotOne can now return screenshots and HTML in one request

Starting from today ScreenshotOne can return both a website screenshot and the content in one simple API request.

Read more

1 min read

Added support of Slack notifications

Added support of Slack notifications

We added support of Slack notifications to ScreenshotOne. Now you can set up and get Slack notifications when you approach or reach your usage limit.

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.