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
Improved design of the authentication pages

Improved design of the authentication pages

We updated the design of the authentication pages to make them more user-friendly and consistent.

Read more

1 min read

Available in Context7

Available in Context7

ScreenshotOne documentation is now available in Context7.

Read more

1 min read

Failed payment alerts in the dashboard

Failed payment alerts in the dashboard

Starting today, you will see an alert in the dashboard when a payment fails.

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.