Daily, I work as hard as I can to ensure that ScreeenshotOne is the best screenshot API out there possible. But I rarely share updates but trust me, a ton of them might go unnoticed. Let's fix this situation.
An improved screenshot history page
Daily, I work as hard as I can to ensure that ScreeenshotOne is the best screenshot API out there possible. But I rarely share updates but trust me, a ton of them might go unnoticed. Let's fix this situation.
Today, I want to share a quick update on the screenshot history page that a few lovely customers requested.
I tried to keep UI as simple as possible for the history page, but it wasn’t enough for a few customers since they were using this page heavily. So, here it goes—the renowned screenshot history page:
I have added the following:
Thanks for your attention, and I hope the new update will help you to use ScreenshotOne more efficiently.
Interviews, tips, guides, industry best practices, and news.
For the past few days, I have been working on improving the stability and performance of the ScreenshotOne API. I started from low-hanging fruits—moving validations and access key management from rendering services to ScreenshotOne's API gateway. The API will be more stable and performant as a result. If you are curious why, please continue reading.
A new version of the ScreenshotOne API has been just deployed. It allows you to include the shadow DOM contents when requesting the page content.
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!
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.