The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use Make’s HTTP > Make a request module to call a screenshot API that does not have a suitable native Make app. The API provider determines the endpoint, HTTP method, authentication, capture parameters, and response format; there is no universal screenshot-API request that works for every service. Once you know whether the response is binary image data, JSON, or a URL, you can map it to the next module or download it as a file.
Choose a native Make app or an HTTP request
First check whether Make offers a provider-specific app with the capture action and options your scenario needs. A native module can reduce setup if its inputs and outputs fit your workflow. Make lists an official, vendor-maintained GetScreenshot app with actions for full-page and element screenshots, usage lookup, and emailing captures: GetScreenshot for Make.
As an Amazon Associate I earn from qualifying purchases.
If no suitable native module exists—or the provider’s API offers options the app does not expose—use Make’s HTTP app. It can connect to API services without a Make integration and supports authenticated and unauthenticated requests. See Make’s HTTP app documentation.
Make also lists a ScreenshotOne connector at its app documentation, which identifies the connector as community developed and says Make does not maintain or support it. Check its current support and capabilities before relying on it.
Build the scenario around the screenshot response
- Choose a trigger. Start with whatever supplies the page URL: for example, a form submission, webhook, schedule, or another app. A screenshot API does not require one particular trigger.
- Add the capture step. Choose the provider’s native Make module if it exposes the action and options you need. Otherwise, add HTTP > Make a request.
- Configure the provider’s request contract. Use the full HTTPS endpoint, method, authentication method, target URL, and capture settings specified in that provider’s current API documentation. These details vary between services.
- Protect the API key. Where Make’s supported authentication configuration applies, use its dedicated Credentials field rather than putting credentials in headers or query parameters. Follow the provider’s authentication instructions too. Avoid exposing keys in shared scenario URLs, public blueprints, or screenshots.
- Inspect the module output. Run the scenario with a test URL and determine whether the response is binary file data, JSON, or a URL. Do not map an assumed output format.
- Route the result. Send binary file data to a downstream module that accepts files. If the provider returns a usable file URL instead, use Make’s Download a file module when you need to fetch it. Parse or map JSON according to its actual structure. Make documents the HTTP app and its file-related options at apps.make.com/http.
- Handle failed requests. Inspect the run output and configure the HTTP module’s option to return an error when the response is 4xx or 5xx if that suits your scenario’s error-handling design.
Example request contract: ScreenshotOne
This is one provider-specific example, not a universal screenshot API setup. ScreenshotOne’s getting-started documentation shows a GET request to https://api.screenshotone.com/take with a target url and an access_key. Its API also accepts POST requests with options in a JSON body. Follow ScreenshotOne’s getting-started guide for the current request details.
ScreenshotOne documents its access key as organization-scoped and says it can be sent in a query string or a POST JSON body. Its key instructions are at ScreenshotOne API keys. In Make, prefer dedicated credential handling when the supported authentication setup fits the provider’s contract; do not leave a real key exposed in a scenario that will be shared.
Choose the right response handling
ScreenshotOne documents PNG, JPEG, WebP, PDF, and other output formats. Its default by_format response returns the selected representation as binary data; other response modes behave differently. Configure the next Make module accordingly: binary output should be treated as a file, while a JSON response or hosted URL needs the appropriate parsing or download step. See ScreenshotOne’s options documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
ScreenshotNeo as an alternative
ScreenshotNeo is a website screenshot API and MCP server. If you want a direct API call rather than configuring a browser or capture service yourself, Make’s HTTP module can call its endpoint. The example below requests a WebP capture of Stripe; replace the target URL with the one supplied to your scenario and keep the access key in Make’s credential storage where the request setup permits.
Or skip the browser setup:
Configure Make’s HTTP request as a GET to https://api.screenshotneo.com/v1/shot, with query parameters access_key and url. For example, the equivalent cURL request is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request setup and response handling. ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and whether the capture was billed. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Troubleshoot common setup failures
- Wrong endpoint or method: Screenshot APIs do not share a standard endpoint or HTTP method. Check the chosen provider’s current API instructions and match the configured request to them.
- Authentication failure: Verify that the key belongs to the correct account or organization and is sent in the location the provider expects. For ScreenshotOne, keys are organization-scoped; see its key documentation.
- The next module rejects the output: Inspect the capture module’s actual output. Binary data, JSON, and a URL require different mappings; use Download a file only when you have a usable file URL.
- A request returns an HTTP error: Check the provider’s status and error response, then review the endpoint, method, credentials, target URL, and request parameters. Make’s HTTP app can be configured to return an error for 4xx and 5xx responses. ScreenshotOne documents its status and JSON error behavior in its getting-started guide.
- A shared scenario reveals a secret: Remove exposed keys from public URLs, screenshots, or blueprints; store credentials using Make’s dedicated credential handling where supported, and rotate a key if it has been disclosed.
Plan for reliability, speed, and usage
Each capture depends on both Make’s scenario and the screenshot provider’s request and response behavior. During setup, test the exact URL and output format your workflow will use, and decide how the scenario should handle provider errors rather than assuming every request produces an image. If the provider returns a URL rather than file data, account for the extra download step in the route.
Rank #4
Before scheduling a workflow at scale, check the provider’s current limits and pricing, the Make module’s available options, and whether the chosen native connector is maintained by the provider or by the community. Current usage limits and prices are not established here, so verify them with the provider rather than relying on an assumed quota.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Does a screenshot API require a particular Make trigger?
No. Use the trigger that supplies the target URL, such as a form, webhook, schedule, or another app.
Can I use ScreenshotOne’s endpoint with any screenshot provider?
No. Its endpoint and parameters are ScreenshotOne-specific; use each provider’s own current API contract.
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.
Recommended Free Tools
