Dashboard actions migrated to oRPC

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

Changelog 1 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
Better and more extensible PDF rendering

Better and more extensible PDF rendering

ScreenshotOne supports PDF rendering for a long time but it was used till recently by a small group of customers. Growing demand in PDF rendering required updating the API. And today, we introduce new options for PDF customization.

Read more

1 min read

ScreenshotOne integration with Dirstarter

ScreenshotOne integration with Dirstarter

Build a directory with Dirstarter and add website screenshots automatically with ScreenshotOne.

Read more

1 min read

Stop scrolling screenshots when a given selector is visible

Stop scrolling screenshots when a given selector is visible

New options were added to the ScreenshotOne API to stop scrolling screenshots when a given selector is reached.

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.