The Screenshot API allows developers to capture full-page or viewport-based screenshots of any publicly accessible URL.

To ensure reliability and speed, especially for pages with heavy scripts or slow load times, our API follows an asynchronous two-step flow. When you make a request, the screenshot job is queued instantly, and we return either the screenshot or (for slower pages) a result URL you can poll to retrieve the result.

You can capture any public webpage over HTTP or HTTPS. Private, gated, or authentication-required URLs are not currently supported.

Yes. You can specify full_page: true in the request parameters to capture an entire scrollable page, not just the viewport.

Use the GET endpoint in our docs and set the parameters as follows. 1. url: string 2. full_page: pass either “true” or “false” (default is false) 3. viewport_width: integer (default is 1920) 4. viewport_height: integer (default is 1080) 5. delay_ms : integer (default is 0) 6. css_classes_to_hide: a string of “space separated” css classes (no dots required. Eg: “container nav-bar chat-popup”

Once you make your we will either send you the screenshot URL or a result URL to check the status of your screenshot task. This result URL will returns either a completed screenshot URL or a status indicating it’s still processing. No authentication is required to access this “result URL”

Most screenshots are ready in 2–6 seconds, but webpages that are slow to load / media asset heavy may take longer.

Yes, use the delay_ms parameter to delay the capture by a specific number of milliseconds. This is useful for waiting on animations or content that takes a while to load.

Yes. Pass an array to css_classes_to_hide with selectors you want hidden (e.g., ads, popups) before capture.

Users can customize their requests by setting parameters such as "full_page," "viewport_width," "viewport_height," "delay_ms," and "css_classes_to_hide" to tailor the screenshot capture to their specific needs.

The Screenshot API returns a JSON object containing the HTTP status code and the URL of the generated screenshot image. For example, a successful response includes fields like "status_code" and "screenshot_url."

The key fields in the response data are "status_code," which indicates the success of the request, and "screenshot_url," which provides the direct link to the captured screenshot image.

The response data is structured in JSON format, with key-value pairs. The "status_code" indicates the request's outcome, while "screenshot_url" contains the link to the image, making it easy to parse and use programmatically.

The endpoint accepts parameters such as "url," "full_page," "viewport_width," "viewport_height," "delay_ms," and "css_classes_to_hide." These allow users to customize their screenshot requests based on specific needs.

Users can utilize the returned data by checking the "status_code" to confirm success and using the "screenshot_url" to display or store the image. This is useful for monitoring website changes or generating previews.

Typical use cases include generating visual previews for marketing materials, automating website testing, capturing visual archives for documentation, and monitoring website changes over time.

Data accuracy is maintained through robust error handling and status code reporting. The API ensures that only successfully captured screenshots are returned, allowing users to trust the output.

If an error status code is received, users should check the URL for correctness and ensure the page is publicly accessible. They can also refer to the API documentation for troubleshooting common issues.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.