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!
The problem was that not every possible error was covered and sometimes ScreenshotOne users couldn’t find more information about unknown errors.
Since today, every possible error has been covered in the API and will be shown in the request log.
In case, a new error type appears, we will add it to the error documentation and to the request log.
Enjoy! And thanks for being a ScreenshotOne customer.
New features, bug fixes, and optimizations...
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.
2 min read
You can now create and save presets in the ScreenshotOne Playground!
1 min read
Integrate ScreenshotOne to render website screenshots with any LLM that supports MCP.
3 min read
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.