Dashboard actions migrated to oRPC

We migrated core ScreenshotOne dashboard actions from API routes and Server Actions to oRPC.

Changelog1 min read

Written by

Dmytro Krasun

Published on

We migrated core ScreenshotOne dashboard actions from API routes and Server Actions to oRPC.

The migration covers important dashboard flows such as API key management, playground presets, storage-related actions and more.

This gives the dashboard a more explicit API surface, better end-to-end typing, and a cleaner foundation for future development. As part of the rollout, we also added safeguards to block Server Actions requests and prevent them from being introduced accidentally again.

If you are curious why and what trade-offs were involved, check out the full write-up in our blog—from API Routes and Server Actions to oRPC in Next.js.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Fixed full page screenshot stitching above max height

Fixed full page screenshot stitching above max height

We fixed full page screenshot stitching so the final image respects `full_page_max_height` more reliably, even when pages report incorrect scroll height.

Read more

1 min read

Add ScreenshotOne to Clay

Add ScreenshotOne to Clay

Generate website screenshots inside Clay to qualify leads, assess content, and enrich rows with visual context automatically.

Read more

1 min read

Better code examples in the playground

Better code examples in the playground

Improved code examples in the playground and added all official supported ScreenshotOne SDKs.

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.