What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Put the screenshot service’s API endpoint in Zapier’s request URL field, then pass the page you want to capture—including its own query string—as the value of the API’s url parameter. In Zapier’s API Request action, add that parameter in Query string parameters, not by appending it to the request URL. Zapier says parameters in the dedicated fields are encoded and appended; parameters typed into the URL field may be ignored.
Keep the API endpoint separate from the page URL
A screenshot request involves two different URLs:
- Request endpoint: the screenshot provider’s API address. Zapier sends the HTTP request here.
- Target page URL: the website address to capture, including any query parameters belonging to that page. This is passed to the API as the value of its documented
urlparameter.
For example, if the page to capture is https://example.com/products?item=42&view=compact, map that entire address as the url parameter value. Do not use it as the API request endpoint, and do not split its item or view parameters into separate screenshot API fields unless that provider’s documentation specifically requires it.
Set up the request in Zapier
- Add an API request action. In Zapier, add the API Request action or a Webhooks by Zapier action that can make the HTTP request. The available options and interface may depend on your account and current Zapier availability.
- Enter the screenshot API endpoint. In the request URL field, use the exact endpoint documented by your screenshot provider. Do not put the target page URL in this field.
- Choose the method the provider documents. Use GET with query parameters if the API supports that pattern. If its instructions require POST with JSON, select POST and use the documented body structure instead.
- Add the target URL parameter. For the API Request action, open Query string parameters. Add
urlas the parameter name and map the trigger field containing the complete target page URL as its value. Add any capture options as separate parameters only if the provider supports them. - Configure authentication and any required headers. Match the screenshot provider’s requirements and choose an authentication method available in the Zapier action you are using.
- Test the action. Use a representative page URL that has both
?and&in its query string. Inspect the test response for a successful capture and confirm that the next Zap step receives the response format it expects.
Zapier’s API Request guide says that parameters entered in its dedicated query parameter fields are URL-encoded and appended to the request. It also warns that parameters added directly to the URL field may be ignored. See Zapier’s Create an API Request action and Send API requests in Zap workflows guides.
Pass a target URL that already has query parameters
Map the complete target URL as one value for the screenshot API’s url parameter. Let Zapier construct the outer request query from its parameter fields rather than manually concatenating a nested query string.
Test with a URL representative of your real workflow, such as one containing multiple page parameters. Confirm that the screenshot shows the intended page state. Zapier documents its parameter encoding behavior, but how a screenshot provider parses the received URL depends on that provider’s API.
Use POST JSON when the provider requires it
Some screenshot APIs accept parameters on a GET request, in a POST JSON body, or both. Advanced capture options may be available only with one method. If the provider documents a POST JSON pattern, select POST and map the target URL and options into a valid JSON body with the exact field names and nesting that the provider specifies. Do not assume the query-parameter setup for GET also applies to POST. The reviewed Screenshot API REST reference is one example of provider documentation that describes both GET query parameters and POST JSON, with some advanced options restricted to POST; it is not a universal API contract.
Choose between API Request and Webhooks by Zapier
Zapier’s API Request action and Webhooks by Zapier can both make API calls, but follow the input guidance for the particular action you choose.
| Zapier action | Where to put parameters | Payload choices |
|---|---|---|
| API Request | Use Query string parameters for query parameters; Zapier documents that these are encoded and appended. | Follow the action and provider’s method and body requirements. |
| Webhooks by Zapier | Zapier recommends putting URL parameters in the data fields rather than adding them to the URL field. | The webhook guide lists Form (URL-encoded), JSON, XML, and Raw payload options. Choose the one the screenshot API documents. |
See Zapier’s Send webhooks in Zap workflows guide for webhook payload guidance and Ways to make API requests in Zapier for its comparison of request options and credential storage.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsHandle authentication and credentials carefully
The screenshot API determines which credentials are required. Zapier says API by Zapier supports OAuth2, API keys in headers, API keys as query parameters, or no authentication, with credentials stored in an app connection. Its comparison says Webhooks credentials are stored in the step or tool setup. Use the method supported by the screenshot API; if it offers a header-based method, avoid exposing a production key in a URL. Check both Zapier’s current action guidance and the provider’s authentication documentation before publishing a Zap.
Zapier’s documentation updated June 29, 2026 describes API by Zapier as beta and says a paid account is required. Availability and interface details can change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot failed or incorrect captures
- The API says the target URL is missing. Check that the parameter name matches the provider’s documentation—often
url—and that it is mapped in the action’s query parameter fields or the required POST body. - The target page’s query string appears broken. Map the full page URL as one parameter value. Avoid manually encoding or concatenating nested parameters unless the provider explicitly instructs you to do so.
- The request goes to the wrong address or ignores parameters. Confirm that the request URL contains only the screenshot API endpoint and move API parameters out of that field into the dedicated query fields or documented body. Zapier warns that URL-field parameters may be ignored.
- The API rejects the request method or options. Check whether the provider supports the chosen GET or POST pattern and whether the capture options you used are available for that method.
- The API returns an authentication error. Verify the credential, its placement (header, query parameter, or connection), and any required headers against the provider’s documentation.
- The test succeeds but the next step cannot use the result. Inspect the response data from Zapier’s test and map the correct output field or file into the next action. The screenshot provider controls the response format.
Or skip the browser setup
ScreenshotNeo is a screenshot API and MCP server for developers. Its one-call GET endpoint accepts a target URL and returns a PNG, JPEG, WebP, or PDF. In Zapier, use its endpoint as the request URL and pass your mapped target page URL as the url query parameter:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpAdapt the target URL and authentication to your Zapier mapping; the ScreenshotNeo API documentation has the endpoint and parameter details. ScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Frequently Asked Questions
Can I put the target page URL in Zapier’s request URL field?
No. The request URL should be the screenshot API endpoint; pass the target page as the API’s documented URL parameter.
Does Zapier automatically encode query parameters?
Zapier says parameters entered in the API Request action’s dedicated query parameter fields are URL-encoded and appended. The screenshot provider’s parsing behavior remains provider-specific.
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.
