New:

• Added the setOnLoadJavascript() method.

We added new methods that allow to specify image compression and DPI:

• setConvertImagesToJpeg()
• setJpegQuality()
• setImageDpi()

Fixes:

• Trailing blank pages were not discarded when a non-default PDF page background color was used.
• PDF was not linearized correctly when viewer preferences were set.

New:

• Added the setClientCertificate() method.
• Added the setClientCertificatePassword() method.
• Added the setHttpProxy() method.
• Added the setHttpsProxy() method.
• Added the setPageBackgroundColor() method.

Fixes:

• Python API client: correct handling of custom string classes, e.g. SafeText in Django.
• Converter: using the 'pdfcrowd-remove' and 'pdfcrowd-hide' CSS classes with the setElementToConvert() method works correctly now.

• Mobile friendly web.
• The online conversion form offers more customization settings.
• Added example integrations of our API with several web frameworks.
• API client libraries:
  • .NET client is now available on NuGet.
  • Node.js: enhanced error reporting in default handlers.
  • PHP: autodetect availability of file_get_contents and cURL.

• We released an API client library for the Go language. The library supports API v2.
• We fixed an issue with large PDFs caused by suboptimal image encoding.

Changes:

• added the setTag() method
• the Java client library can run on Android

Changes:

• Use a fallback if cURL is not found.

Changes:

• PHP: The client throws an exception if the local file can't be written.
• All: More descriptive SSL error messages.

Changes:

• Added the setDisableSmartShrinking method.

Overview

The Pdfcrowd API v2 is the new generation of our API. It is not 100% backward compatible but the changes are mostly syntactic and the migration from API v1 should be straightforward.

If you want to switch your current API v1 plan to API v2, please follow these steps:

1. Activate the free API v2 trial in your account page.
2. Follow the instructions below and migrate your API v1 implementation to API v2.
3. If the API v2 works to your satisfaction, choose from our API v2 plans.
4. If you no longer need the API v1 implementation, you can cancel the API v1 plan.