Better validation error messages

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

Changelog1 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
Improved full-page screenshot rendering

Improved full-page screenshot rendering

Fixed a few issues related to full-page screenshots rendering.

Read more

1 min read

Multiple notification recipients

Multiple notification recipients

Add multiple dedicated email recipients for usage limit notifications.

Read more

1 min read

Add ScreenshotOne to n8n workflows

Add ScreenshotOne to n8n workflows

You can now use ScreenshotOne in n8n workflows to render website screenshots, PDFs, scrolling screenshots and videos.

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.