
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!
- Written by
- Dmytro Krasun
- Published on
Automate Website Screenshots
Guides, Product Updates, and Helpful Resources from ScreenshotOne.
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!
A new and improved request log has been deployed. That is a good beginning of the week! Check out why.
From today, you can get parsed Open Graph metadata and screenshots in one API request.
You can record a page navigation when recording scrolling screenshot video. It allows render less boring and more engaging videos.
Now, errors will have relevant documentation links. It will be also possible to see why some requests failed in the dashboard and get recommendations on how to address the issue.
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.
There is a set of use cases when you want to fail screenshot rendering and retry it if the content of the page contains a string.
We just released an updated version of our algorithm to block cookie banners by heuristics.
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.