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 error coverage and documentation

Better error coverage and documentation

Since a few months ago, it has been possible to check errors in the dashboard request log and get explanations and more details in the documentation. But!

Read more

1 min read

Use cases in the ScreenshotOne playground

Use cases in the ScreenshotOne playground

Having documentation and code examples is great, but not enough to allow developers to quickly integrate the API and assess all available features of the ScreenshotOne API.

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.