![screeenly](https://3.screeenly.com/img/screeenly-3-logo.svg?v=2) [← All posts](https://3.screeenly.com/blog) Changelog API changes in November 2026 ============================ SZ Stefan Zweifel · Nov 6, 2026 · 2 min read This post lists every change to the API that shipped with the [redesign](https://3.screeenly.com/blog/redesign). Caching and the longer file retention have [their own post](https://3.screeenly.com/blog/caching). Block ads and trackers while a page loads ----------------------------------------- Two new options stop the browser from loading resources you don't need: - `block_urls`: skip every request whose URL contains one of these strings. - `block_domains`: skip every request to these domains. ```bash curl --request POST \ --url https://3.screeenly.com/api/v1/shots \ --header "Authorization: Bearer $TOKEN" \ --data url=https://example.com \ --data "block_domains[]=googletagmanager.com" \ --data "block_urls[]=/ads/" ``` Both accept up to 50 entries. They work for screenshots, PDFs and rendered HTML, and in the playground. New maximums ------------ Some options could be set to values that Chrome can't render, or that made a request run for minutes. They now have limits. A request above a limit fails validation with a `422`, which doesn't count toward your usage. FieldMaximumScreenshot size16,384 pixels per side and 40 megapixels in total. The window or clip size is multiplied by `device_scale_factor` first.`clip_width`, `clip_height`Same as the screenshot size. They had no limit before.`paper_width`, `paper_height`5,000 mm (was 100,000 mm)`html`2,000,000 characters`header_html`, `footer_html`100,000 characters each`http_headers`, `cookies`, `block_urls`, `block_domains`50 entries eachHeader values / cookie values8 KB / 4 KB A 1440 × 900 window at `device_scale_factor=3` is 4320 × 2700 pixels, or 11.7 megapixels, and still works. A 10,000 × 10,000 window at 3× doesn't, and never produced a usable image anyway. Request IDs ----------- Every response now has an `X-Request-ID` header, also when the request failed. Send your own ID in the same header to retry a request safely: a repeat with the same ID returns the first response and isn't charged again. The [caching post](https://3.screeenly.com/blog/caching) explains how it works. Include the request ID when you email support about a request. We can find it in our logs right away. Token abilities --------------- API tokens now have abilities, and the API checks them: - `shot:create` creates screenshots, PDFs and rendered HTML. The API needs it. - `shot:read` lists your captures and reads your usage over the [MCP server](https://3.screeenly.com/blog/mcp-server). `shot:create` includes `shot:read`. Every existing token has `shot:create` and keeps working. Requests that fail validation are free -------------------------------------- A request that fails validation, for example with a missing `url` or a `window_width` that's too large, no longer counts toward your usage. Requests that fail while rendering or time out still count, because the browser already ran. New response headers -------------------- HeaderValue`X-Request-ID`The ID of the request`X-Cache` `HIT` when the result came from the cache, `MISS` otherwise`X-Request-Replayed` `true` when the response is a replay of an earlier request with the same ID`X-Usage-Remaining`Requests left this month`X-Credits-Remaining`Your credit balance Fixes ----- - On the 29th to the 31st of a month, the reset date in `X-Usage-Resets`, `meta.usage_limit.resets` and the dashboard was one month too late. It's correct now. - Many requests sent at the same moment could go past the monthly limit. The limit is now checked and counted in one step. The [API reference](https://docs.3.screeenly.com/reference/) lists every option with its limits. Questions? Email support@screeenly.com. SZ [Stefan Zweifel](https://stefanzweifel.dev) is a fullstack developer based in Zurich, Switzerland and the creator of screeenly. More posts [ Nov 6, 2026 · Journal Let your agent take screenshots ](https://3.screeenly.com/blog/mcp-server) [ Nov 6, 2026 · Changelog Identical requests are now free ](https://3.screeenly.com/blog/caching) [ screeenly Screenshots, PDFs and rendered HTML from one API. Start for free → ](https://3.screeenly.com)