Skip to main content

Pritset SDKs are now available for six programming languages

· 3 min read
Yurii Molchanov
Yurii Molchanov
Founder of Pritset

Alt text

Pritset now provides official SDKs for Node.js, PHP, Python, Go, .NET, and Java, along with runnable examples for every supported language.

This release is focused on one goal: making it easier for development teams to integrate DOCX-to-PDF generation into their existing applications.

From API endpoints to language-native integrations​

A documented API provides the foundation for an integration, but developers still need to configure authentication, construct requests, handle errors, and translate API responses into the conventions of their language.

The new Pritset SDKs provide language-specific interfaces for the complete template and document generation lifecycle.

Developers can use them to:

  • Validate DOCX templates before uploading them
  • Create and manage reusable templates
  • List and retrieve template information
  • Update existing templates
  • Download stored templates
  • Generate PDFs directly from JSON data
  • Submit asynchronous PDF generation requests
  • Delete templates that are no longer required

All six SDKs are currently aligned on version 0.1.5 and follow the same Pritset API contract. This keeps the available operations and expected behavior consistent across languages while still following each ecosystem’s conventions.

Available SDKs​

Official Pritset SDKs are now available for:

  • Node.js
  • PHP
  • Python
  • Go
  • .NET
  • Java

Each SDK has language-specific installation instructions, configuration examples, API documentation, and error-handling guidance.

Explore the SDK documentation at:

https://pritset.com/docs/sdks

Tested against the production API​

Each SDK has completed the same production lifecycle test against the Pritset API using a dedicated test account.

The test validates the integration from beginning to end, including template validation, creation, retrieval, updating, downloading, PDF generation, and cleanup.

Production lifecycle testing is also integrated into the GitHub pull request workflow for each SDK. Changes targeting the main branch are tested before they are merged, helping us detect differences between an SDK implementation and the live API.

Runnable examples for every language​

Documentation is useful for understanding individual methods, but a complete working project is often the fastest way to evaluate an SDK.

The updated Pritset examples repository now contains standalone projects for all six supported languages. Each example:

  • Uses the language’s standard package manager
  • Loads credentials from environment variables
  • Demonstrates a complete DOCX-to-PDF workflow
  • Keeps generated PDF files out of version control
  • Can be used as a starting point for a real integration

The examples are intentionally small so developers can focus on the Pritset workflow without first understanding a larger application.

Browse the examples at:

https://github.com/daviatorstorm/pritset-examples

Improvements to the Pritset dashboard​

We have also updated the Pritset frontend to make template development and account monitoring easier.

The latest improvements include:

  • A more responsive dashboard across different screen sizes
  • Clearer hourly, monthly, and per-template usage statistics
  • Browser-based previews for uploaded DOCX templates
  • Template testing with custom JSON data
  • Generated document previews before integration
  • Easier copying of template IDs into application code

These changes make it possible to prepare and test more of the document generation workflow from the dashboard before connecting an application through an SDK.

Start building with Pritset​

Choose your preferred language, install the corresponding SDK, and follow its quick-start guide to generate your first PDF from a DOCX template.

SDK documentation:
https://pritset.com/docs/sdks

Runnable examples:
https://github.com/daviatorstorm/pritset-examples

Try Pritset:
https://pritset.com/docx-to-pdf