Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsScreenshotAPI.net’s public documentation describes screenshot requests and their HTTP responses, but it does not verify an outbound webhook or callback URL. If you need a result, make the API request and handle its response. If your application requires a later notification to a URL you supply, confirm current support and delivery details with ScreenshotAPI before building around it.
Does ScreenshotAPI.net support webhooks?
The official materials reviewed describe a request/response integration. They do not establish whether ScreenshotAPI.net offers a separate option that sends an HTTP request to your server when a screenshot is ready. That documentation gap is not proof the feature is unavailable: it could exist in an account-specific or undocumented form. Confirm with the vendor rather than assuming either support or non-support.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
APIs and Webhooks for Beginners: Connect Apps, Automate Tasks, and Build Useful Integrations | $2.99 | Buy on Amazon |
| 2 |
|
Shelly Pro 3EM 3CT 63 Wi-Fi & LAN 3-Phase Smart Energy Meter | $150.99 | Buy on Amazon |
A webhook or callback URL usually means your application gives a service a URL, and the service makes a later outbound request to it. That is different from the ordinary HTTP response returned to the application that initiated a screenshot request.
What does ScreenshotAPI.net document instead?
Send a render request and handle the response
The v3 render documentation shows a GET request to https://shot.screenshotapi.net/v3/screenshot with token and URL parameters. The getting-started guide documents GET and POST, and lists JPEG, PNG, WebP, and PDF output options. Use the current endpoint documentation for the exact parameters and request format: getting-started documentation.
#1 Best Overall
The receiving application can process the HTTP response when the request completes. This is a synchronous request/response pattern from the caller’s perspective; the documented output modes alone do not establish asynchronous job execution or a later server-to-server notification.
Choose IMAGE or JSON for the result you need
| Mode | What the response contains | When it fits |
|---|---|---|
| IMAGE | Raw screenshot bytes in the response body. | When the caller needs the image file itself. |
| JSON | A hosted screenshot URL and metadata. | When a workflow needs a result reference and metadata to store or pass along. |
The official Playground presents JSON as useful for automated workflows that need a hosted URL and status metadata. A hosted URL is not a webhook: your server still receives it as part of the API response. See the ScreenshotAPI.net Playground for its response-mode description.
Is a render wait event a callback?
No. A render wait setting controls when the browser captures the target page; it does not, by itself, notify your application. ScreenshotAPI.net documents wait_for_event as a way to wait for a point in the target page’s loading lifecycle, while JavaScript injection runs in the target browser context before capture. Neither description establishes an outbound request to a caller-supplied URL. See the vendor’s pages on wait events and JavaScript injection.
How should you build an integration that needs completion notification?
- For a direct result, send the documented render request and process its HTTP response. Choose IMAGE for bytes or JSON for a hosted URL and metadata.
- If the caller cannot remain open while rendering, do not treat JSON mode or a wait event as proof of asynchronous completion. Ask ScreenshotAPI support whether a webhook or callback URL is currently available.
- Before relying on a callback, get the exact parameter name, supported authentication, payload schema, delivery guarantees, retry policy, timeout behavior, and whether the feature is enabled for your account. These details are not established by the reviewed public materials.
- Design for failure, regardless of response mode: handle non-success HTTP responses and timeouts, avoid assuming a result URL is permanent, and provide a way to retry or reconcile work if your application misses a response. Do not label a self-managed polling or queue design as a ScreenshotAPI webhook.
Other operational details that affect workflows
- Cache: ScreenshotAPI.net’s help material says cached requests do not count toward quota unless you opt to request only fresh screenshots. It describes retention of up to 30 days on the free tier and six months on paid tiers; verify current plan terms before depending on these changeable limits. See the help page.
- API keys: The same help material says rolling an API key in the dashboard revokes the previous key. It also says domain restriction for keys was unavailable when that answer was written; check current account controls rather than assuming the limitation remains.
- Performance and uptime: ScreenshotAPI.net’s features page makes vendor claims of a 99.9% uptime SLA and sub-3-second average render time. The material reviewed does not show a publication year or independent measurement. Treat these as vendor claims and verify SLA terms directly before using them as service guarantees. See the features page.
ScreenshotAPI.net troubleshooting
You expected a callback, but nothing arrived
The reviewed public documentation does not confirm an outbound callback option. Check whether your account or current API documentation explicitly offers one, then ask support for the delivery contract. A returned image or JSON response is not evidence that a later notification will be sent.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchYour automation needs a file but receives JSON
Check the configured response mode. JSON provides a hosted URL and metadata; IMAGE returns the screenshot bytes in the response body. Configure the mode that matches the receiving code.
Rank #2
- The Shelly Pro 3EM 3CT 63 is a next-gen DIN rail-mountable energy meter for single or three-phase installations, featuring a 63A, 3-phase current transformer for non-contact measurements. It supports 4-quadrant measurement, optical pulse indication of energy usage, and is photovoltaic-ready. *It doesn't have a built-in relay; contactor control requires a Shelly Pro Addon attached to the device.
- Professional Smart Meter - Shelly Pro 3EM-3CT63 is a professional smart meter that reports accumulated energy, voltage, current, active, and apparent power per phase in real time. It stores data for up to 60 days in 1-minute intervals and includes a real-time clock to maintain accurate time if the SNTP server connection is lost.
- Ideal for business energy measurement - In commercial buildings, it helps monitor energy usage across floors or departments allowing accurate cost allocation and identification of energy wastage. In manufacturing plants it tracks energy consumption of heavy machinery, optimizing usage to reduce operational costs. For store owners it monitors energy usage of systems like lighting, HVAC § refrigeration, helping to identify inefficiencies § reduce energy bills while supporting sustainable practices
- Shelly Customer Service - Shelly is one of the fastest-growing Smart Home brands in the world with devices, providing solutions for the automation of private homes, buildings and businesses. We provide our customers with professional support and a 5 years device warranty.
- Shelly Smart Control App will help you control your Shelly devices remotely and will send notifications for all automated events in your home. You can easily configure devices and manage their settings individually, or you can create personalized scenes by combining Shelly devices to trigger certain actions in your home automation.
The result is stale or a request affects quota unexpectedly
Check whether the request is using cached output or asking for a fresh screenshot. The help page describes different quota treatment for cached and fresh requests, but plan rules can change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you would rather use an API that explicitly reports capture outcomes in response headers, try ScreenshotNeo: it removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed; and its MCP server lets AI agents take screenshots. It provides 1,000 screenshots a month free with no card, and paid plans start at $5 for 3,000.
One GET request returns the screenshot file; see the ScreenshotNeo API documentation for options.
Recommended Free Tools
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSign up for 1,000 free screenshots a month, with no card required.
Frequently Asked Questions
How do I get notified when ScreenshotAPI.net finishes a screenshot?
The reviewed public materials do not verify a callback URL or other outbound completion notification. Ask ScreenshotAPI support to confirm current options and delivery details before implementing one.
Does ScreenshotAPI.net return a URL or the image itself?
It documents both modes: IMAGE returns the screenshot bytes in the response body, while JSON returns a hosted URL and metadata.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
