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.
Written by
Dmytro KrasunPublished on
The goal of the new improvement is to make the API self-service as much as possible and to reduce the support load.
It will help ScreenshotOne customers to get unstuck and not wait for the support team to answer questions and analyze the problem themselves quickly.
Also, a reduced support load will help ScreenshotOne to provide better services and more delightful features.
Documentation links in the response
Since now you can the documentation URL in the error response. It will allow users to check how to handle the error straight away:
Improved history
In the dashboard request log, users will also see an error and it is a link to the dedicated documentation page:
Next
There is a lot to do, still:
- Today, only a handful of errors are covered. But it is a good start and a solid foundation. The goal is to cover all errors.
- Send an email when the error is encountered for the first time with help on how to handle it.
- Automatically analyze the error and what caused it and provide code examples on how to fix it.
- More analytics of error rate by error types.
Any more ideas or best practices you can share? Feel free to reach out and share at hey@screenshotone.com.
Read more product updates
Interviews, tips, guides, industry best practices, and news.
Better and more extensible PDF rendering
ScreenshotOne supports PDF rendering for a long time but it was used till recently by a small group of customers. Growing demand in PDF rendering required updating the API. And today, we introduce new options for PDF customization.
Improved the behavior and stability of the "scroll_into_view" option
Before the change, there was a subset of cases when the rendering requests were failing when using the scroll_into_view option. Now, it is improved and will make rendering more stable.
Extract Open Graph metadata while rendering screenshots
From today, you can get parsed Open Graph metadata and screenshots in one API request.
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.