Changelog
Changes to the API that can affect your integration. Additions that change nothing for existing calls are listed too.
7 October 2026
- OpenAPI specification 1.0.0: request and response examples for every operation, the
X-Quota-*headers, retry guidance, and per-operation authentication (X-API-Keyeverywhere; Basic auth on/v3/convert/pdfandaccess_keyon/takefor compatibility). The API itself is unchanged. - New pages: pricing, data residency and compliance, and /llms.txt for AI assistants.
24 September 2026
- Self-service accounts: sign in with your email at /en/account and get a Sandbox key at once. Sandbox: 100 renders a month, up to 10 a day (
X-Quota-Daily-*headers). - Plans are enforced per API key: responses carry
X-Quota-LimitandX-Quota-Remaining, and a used-up allowance answers402. Sandbox keys get a watermark. - Security: the browser runs with its sandbox and without secrets in its environment; a firewall inside the container blocks connections to the container itself, including through redirects.
/healthreturns only the status.- Screenshots:
block_ads,block_trackers,block_cookie_banners,block_chats,hide_selectors,block_requestsandblock_resourcesare now supported. Previously they were accepted without effect. - Screenshots:
block_banners_by_heuristicsis now refused with400instead of being ignored. - Logs no longer contain query strings, so keys sent as
access_keyare never written to disk. - Documentation, code examples and the OpenAPI specification published, in Arabic and English.
23 September 2026
- The API runs in production in Jeddah at
https://api.sahifa.dev. POST /v3/convert/pdf, compatible with PDFShift v3.GETandPOST /take, compatible with ScreenshotOne.