A new major release is now available on both our HTML to PDF and Screenshot APIs. The new release is completely backwards compatible with the version 6 on the API surface. However the resulting documents might differ slightly. Please compare the resulting documents to ensure smooth transition.

The version 7 of both HTML to PDF and Screenshot APIs are built on the latest Chromium and a much performant server architecture. The API also employs several key bugfixes that have caused failed API calls on specific websites / option configurations.

We urge all our customers to upgrade to v7 as it offers the best performance and results across our previous versions.

In order to meet the demands of growing user base and increased amount of API calls, we have been working over the clock to improve the server architecture. 

We have finished deploying a major upgrade that should yield faster conversions, more reliable API access, rapid failover in case of an issue and better autoscaling during peak times.

All updates are backward compatible and there is no requirement for an API version bump, if you are using version 5 or 6 of either API, you will automatically benefit from the changes.

We have released a super cool feature for users who frequently run out of quota at the end of the month. 🎉

Your API calls will not fail after your hit your quota and you will continue to use our service at a pre-defined rate based on your plan.

New users will have this feature enabled by default. Current users who want to enable this feature have to navigate to Subscription Plan page under console.

We highly recommend you to upgrade your plan if your usage is much higher than your plan's quota since bigger plans have a lower cost per API call. This feature is useful if your usage is slightly exceeding your quota and you don't want to upgrade your plan.

Moreover, we have a brand new 100k plan for both HTML to PDF API and Screenshot API due to high demand..

It is important to test an API to understand the inner workings before implementing it into an application. While the Restpack APIs have always been approachable, we wanted to make it even more convenient for our users to visually test the API parameters, see results and generate working code samples in a single click.

👉 https://restpack.io/console/product/pdf/api-explorer

👉https://restpack.io/console/product/screenshot/api-explorer

A new major release is now available on both our HTML to PDF and Screenshot APIs. The new release is backwards compatible so we urge our users to simply replace their version to v6 from now on.

Improvements

• width and height parameters on the HTML to PDF API, it is now not necessary. Simply use the pdf_page or pdf_[width|height] parameters for page size customization.PDF page and viewport sizes are now automatically calculated by the API. If you used to set 
• General performance of the API has been improved in 20% range.

New Features

• HTML to PDF API now accepts a pdf_author parameter to customize the author metadata of resulting PDF document.pdf_author
• Now you can choose which pages to be included in your final PDF document. This parameter can contain a single page number or a range in 3-4 format.pdf_page_ranges
• grayscale: Both APIs can create grayscale documents using grayscale=true parameter now.
• pdf_encryption: The HTML to PDF API can now generate encrypted PDF documents. The pdf_encryption parameter can either be 40 or 128 which sets the encryption key length. 40 bit encryption will be more compatible while 128 bit files will be more secure. The encrypted file can have a user and/or owner password and also can be customized with several restrictions. Please refer to our docs for further details.

We now have a brand new user console and API server online, available to all accounts across our products. This change builds on top of countless user feedback we received to make sure everything regarding to your subscription and API usage is as clear and approachable as possible.

You can now obtain more statistics about your API usage in real time, including failed requests and historical data. You can also check each and every API call, detailing the request / response parameters, any errors and metadata received. We believe this will make debugging / integration experience much pleasant.

We have released a major new release on the rendering engine for HTML to PDF API and Screenshot API. It is mostly backwards compatible.

New Features

• privacy** parameter**: If you set privacy=true on your calls. This ensured that we will not store the resulting document or any immediate render for caching or future use. The captured document will be streamed directly to you and will be discarded. Note that this parameter is not compatible with as that requires us to save and host the resulting document.
• cache_ttl** parameter**: The new API has caching disabled by default. We have removed the fresh parameter from the earlier versions. Not every call returns a fresh capture. If you wish to cache documents for repeated calls, please set cache_ttl to maximum number of seconds you wish to cache your resulting documents.

Improvements

The new API is faster and more reliable due to architectural changes. In order to minimize the call latency, we made several changes to our pipeline and you should see the results on your API calls.

Upgrade

In order to switch to the new version, you can simply change your API call url to https://restpack.io/api/html2pdf/v5/convert. If you do not need caching, there would be no more changes required.

Due to popular demand, we decided to enable custom PDF headers and footers on our Startup plan. If you already on the Startup plan, you can immediatly start using these features.

We just added custom filenames support to the API. In order to save your files with a specified filename, you can now pass a filename=xx.png parameter. If you also set json=true, that will return a CDN path ending with your requested filename. Otherwise, we will add a content-disposition header to ensure that client browsers do download the file with the filename that you provide.

We have updated our privacy policy to meet the new EU data protection regulation requirements. We have also created a legal agreement promising the protection of all personally identifiable information and sensitive information that we collect and store.

Privacy Policy

Data Processing Agreement