Check out how to use the external identifier to improve tracking of webhook executions.
ScreenshotOne API now supports the external_identifier parameter. It allows you to track requests and errors (in webhooks) by setting any alphanumeric value.
You will get the result as x-screenshotone-external-identifier header in the webhook request headers.
It is helpful for tracking screenshots or videos errors or successful renders in your application.
If you have any ideas, suggestions or issues on using this feature, please let us know at support@screenshotone.com.
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
Automate website screenshots, animated scrolling captures, and visual documentation workflows with ScreenshotOne and viaSocket.
1 min read
Use the new hover option to interact with elements before rendering, and choose whether to fail if the hover selector is not found.
1 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.