Pdf

It’s simple to use: you only need to submit your access_key and a url url of a webpage. The API will return the pdf of the webpage.

Getting started

REST

The PDF API, like all of ScreenshotMAX’s APIs, is organized around REST. It is designed to use predictable, resource-oriented URL’s and to use HTTP status codes to indicate errors.

HTTPS

The PDF API requires all communications to be secured TLS 1.2 or greater.

API Versions

All of ScreenshotMAX’s APIs are versioned. The PDF API is currently on Version 1.

Your Access Key

Your access key is your unique authentication key to be used to access ScreenshotMAX APIs. To authenticate your requests, you will need to append your access key to the base URL as a query parameter for GET requests. You can also use the X-Access-Key header to pass your access key. You can find your access key in your account dashboard.

Base URL

https://api.screenshotmax.com/v1/pdf

Validation endpoint

ScreenshotMAX’s PDF API simply requires your unique access key and url to be passed in the URL. The API will return a pdf of the webpage.

https://api.screenshotmax.co/v1/pdf
?access_key=YOUR_ACCESS_KEY
&url=https://example.com

This was a successful request, so the API returned a 200 OK response. The pdf is returned in the body of the response.

Request parameters

access_keystringQueryRequired

Your unique access key. You can find your access key in your account dashboard.

urlstringQuery

The URL of the webpage you want to rendering of. Must be a valid URL and accessible from the internet. If the URL contains a querystring, it must be URL-encoded.

Either url or html must be provided.

For example, https://example.com/test?param=1 should be passed as https%3A%2F%2Fexample.com%2Ftest%3Fparam%3D1.

htmlstringQuery

This parameter allows you to provide raw HTML content to render and capture as a screenshot. It must be a valid HTML string.

Either url or html must be provided.

Example: html=<html><body><h1>Hello, World!</h1></body></html>

pdf_paper_formatstringQueryDefault: letter

Available options include: are letter, legal, tabloid, ledger, a0, a1, a2, a3, a4, a5, a6. Use this setting to control the dimensions of the output when generating PDF documents.

pdf_landscapeboolQueryDefault: false

Defines the orientation of the webpage when rendering as a PDF. true for landscape and false for portrait.

pdf_print_backgroundboolQueryDefault: false

Print background colors and images. true to print background colors and images, false to not print background colors and images.

gpu_renderingboolQueryDefault: false

Whether to use GPU rendering. Only available for scale paid plan.

capture_beyond_viewportboolQueryDefault: false

Whether to capture content beyond the viewport.

viewport_devicestringQuery

The device type for the viewport.

viewport_widthnumberQueryDefault: 1280

The width of the viewport in pixels.

viewport_heightnumberQueryDefault: 1080

The height of the viewport in pixels.

viewport_landscapeboolQuery

Whether the viewport should be in landscape mode.

viewport_has_touchboolQuery

Whether the viewport has touch capabilities.

viewport_mobileboolQuery

Whether the viewport is a mobile device.

device_scale_factornumberQuery

The device scale factor for the viewport.

clip_xnumberQuery

The x-coordinate of the top-left corner of the clipping region.

clip_ynumberQuery

The y-coordinate of the top-left corner of the clipping region.

clip_widthnumberQuery

The width of the clipping region.

clip_heightnumberQuery

The height of the clipping region.

block_annoyancestringQueryDefault: cookies_banner

The annoyance to block. Options include none, cookies_banner, ads, tracking.

block_ressourcesstringQuery

The resources to block. Options include document, stylesheet, image, media, font, script, texttrack, xhr, fetch, eventsource, websocket, manifest and other.

media_typestringQueryDefault: screen

The media type for the rendering. Options include screen and print.

vision_deficiencystringQuery

The vision deficiency for the rendering. Options include reduced_contrast, blurred_vision, deuteranopia, achromatopsia.

dark_modeboolQueryDefault: false

Whether to use dark mode for the rendering.

reduced_motionboolQueryDefault: false

Whether to reduce motion for the rendering.

geolocation_accuracynumberQuery

The accuracy of the geolocation in meters. Minimum is 0. Maximum is 1000.

geolocation_latitudenumberQuery

The latitude of the geolocation. Minimum is -90. Maximum is 90.

geolocation_longitudenumberQuery

The longitude of the geolocation. Minimum is -180. Maximum is 180.

hide_selectorsstring[]Query

The selectors to hide in the content. This allows you to remove specific elements from the rendering. Example: hide_selectors=div.header,div.footer.

click_selectorstringQuery

The selector to click in the content. This allows you to interact with specific elements before the rendering. Example: click_selector=button.submit.

attachment_namestringQuery

The name of the attachment, without the extension filename. This is the name that will be used when downloading the response. Extension will be automatically added based on the format parameter.

timezonestringQuery

The time zone for the request. This allows you to simulate different time zones. Available time zones from the IANA Time Zone Database.

authorizationstringQuery

The authorization header to use for the request. This should be a base64-encoded string (e.g., for Basic Auth, encode "username:password" using base64). This allows you to authenticate with the webpage before capturing the content.

user_agentstringQuery

The user agent to use for the request. This allows you to simulate different browsers and devices.

cookiesstring[]Query

The cookies to use for the request. This allows you to simulate different sessions and states. Example: cookies=name=value; name2=value2.

headersstring[]Query

The headers to use for the request. This allows you to simulate different requests and responses. Example: headers=header1:value1; header2:value2.

ip_locationstringQuery

The IP location to use for the request. This allows you to simulate requests from different countries by routing them through proxy servers with corresponding IP addresses. This feature is only available on scale paid plan.

Supported locations:

United States (us)
China (cn)
Europe (eu) (random EU country)
Canada (ca)
Mexico (mx)
United Kingdom (gb)
Germany (de)
France (fr)
Switzerland (ch)
India (in)
Japan (jp)
South Korea (kr)
Russia (ru)
Brazil (br)
Australia (au)

proxystringQuery

The proxy to use for the request. This allows you to route the request through a different IP address. The proxy must be in the format http://username:password@host:port or https://username:password@host:port.

bypass_cspboolQueryDefault: false

Whether to bypass the Content Security Policy (CSP) of the webpage. This allows you to capture content of webpages with strict CSPs.

delaynumberQueryDefault: 0

The delay in seconds before rendering. This allows you to wait for specific elements to load before capturing the content. Maximum is 30.

timeoutnumberQueryDefault: 30

The timeout in seconds for the rendering. This allows you to set a maximum time for the request to complete. Maximum is 30.

wait_untilstring[]QueryDefault: ['domcontentloaded']

The conditions to wait for before rendering. This allows you to ensure that specific elements are loaded before capturing the content. Available options include:

load: Wait for the load event to be fired.
domcontentloaded: Wait for the DOMContentLoaded event to be fired.
networkidle0: Wait for no network connections for at least 500 ms.
networkidle2: Wait for no more than 2 network connections to be active for at least 500 ms.

metadata_iconboolQueryDefault: false

Whether to include the metadata icon in the response. This allows you to capture the favicon of the webpage. The link of the icon will be included in the header X-Screenshotmax-Metadata-Icon.

metadata_titleboolQueryDefault: false

Whether to include the metadata title in the response. This allows you to capture the title of the webpage. The title will be included in the header X-Screenshotmax-Metadata-Title.

metadata_fontsboolQueryDefault: false

Whether to include the metadata fonts in the response. This allows you to capture the fonts used on the webpage. The fonts will be included in the header X-Screenshotmax-Metadata-Fonts.

metadata_hashboolQueryDefault: false

Whether to include the metadata hash in the response. This allows you to capture the hash of the webpage. The hash will be included in the header X-Screenshotmax-Metadata-Hash.

metadata_statusboolQueryDefault: false

Whether to include the metadata status in the response. This allows you to capture the HTTP status code of the webpage. The status code will be included in the header X-Screenshotmax-Metadata-Status.

metadata_headersboolQueryDefault: false

Whether to include the metadata headers in the response. This allows you to capture the headers of the webpage. The headers will be included in the header X-Screenshotmax-Metadata-Headers.

cacheboolQueryDefault: false

Whether to store the content of the rendering in the cache. This allows you to store the rendered content for a specified time-to-live (TTL) period.

cache_ttlnumberQueryDefault: 604800

The time-to-live (TTL) for the cache in seconds. This allows you to set a maximum time for the cached resources to be valid. Maximum is 30 days in seconds (2592000).

asyncboolQueryDefault: false

Whether to use asynchronous processing for the request. This allows you to capture content without blocking the request.

webhook_urlstringQuery

The callback URL for asynchronous processing. This allows you to receive the response via a webhook. The webhook will be triggered when the response is ready. The webhook URL must be a valid URL and must be accessible from the internet. The webhook URL must be HTTPS and must support the POST method. More information about webhooks can be found in the async & webhook documentation.

webhook_signedboolQueryDefault: true

Indicates whether the webhook request should be signed. Enabling this option allows you to verify the authenticity of incoming webhook requests. For more details, refer to the async & webhook documentation.

signaturestringQuery

The cryptographic signature used to verify the authenticity of the request. For more information on how to compute and validate this signature, see the signed requests documentation.

Response and error codes

Error Codes

Whenever you make a request that fails for some reason, an error is returned also in the JSON format. The errors include an error code and description, which you can find in detail below.

Code	Type	Details
200	OK	The request was successful.
400	Bad request	The request was malformed or invalid.
401	Unauthorized	The request was rejected due to an invalid access key or missing signature when signed requests are enabled.
403	Forbidden	The signature provided is invalid. Occurs when signed requests are enabled.
402	Payment Required	Access denied due to an unpaid invoice. Applies to paid plans.
423	Locked	The request was denied due to insufficient quota.
429	Too Many Requests	The rate limit has been exceeded (too many requests per minute).
500	Internal server error	The request failed due to an internal server error.

Getting started​

REST​

HTTPS​

API Versions​

Your Access Key​

Base URL​

Validation endpoint​

Request parameters​

Response and error codes​

Error Codes​