PDFCrowd API Versioning

PDFCrowd uses a multi-level versioning system:

• API versions (v1, v2) - The overall API platform
• Converter versions (24.04, 20.10, etc.) - The conversion engines that process your documents
• Integration versions - Client libraries and plugins that connect to the API

This page explains how these versions relate to each other.

API Major Versions

Frozen indicates versions that no longer receive updates or bug fixes.

Converters

Different converter versions produce different output with varying capabilities. Switching versions may change your document's appearance and behavior. Newer versions provide better support for the latest web technologies and standards.

Best Practice: For new integrations, always use the latest version. Once chosen, use the same converter version consistently to ensure predictable results.

Use getVersion() to check which converter version you are currently using.

API Client Libraries

Client library versions follow semantic versioning (major.minor.patch):

• Patch - Bug fixes and minor changes, no API changes
• Minor - New features, backward-compatible
• Major - Breaking changes, may require code updates

Each client library version uses a specific default converter version. This ensures compatibility out of the box. You can override the default using the setConverterVersion() method if you need a specific converter version for your use case.

WordPress Plugins

Plugin versions follow semantic versioning (major.minor.patch), similar to the API client libraries. Plugin version numbers are independent from client library versions.