You can now get a screenshot URL in the response of the API call.
We have added a new field to the response of the API call: screenshot_url.
This field contains a URL to the screenshot of the rendered page.
Before the change, you needed to use cache to get the screenshot URL via the cache_url field. Now, you can get it directly in the response every time you request a screenshot with response_type=json.
Read more in our documentation on how it works.
If you have any questions or need any assistance, please, reach out at support@screenshotone.com.
New features, bug fixes, and optimizations...
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.
1 min read
Email and password authentication, email change flow, email verification, GitHub authentication, and improved UX/UI.
6 min read
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.
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.