What's New

• Compatibility: No API or schema changes in 1.9.6 — existing endpoints and models remain unchanged so your current integrations continue to work.
• Upgrade: You can upgrade to v1.9.6 as a safe drop-in replacement for v1.9.5 with no code changes required.
• Scope: There are no new capabilities or endpoints in this release.

Generated from TemplateFox API v1.9.6

What's New

• No user-facing changes: There are no new features, endpoints, or model changes in v1.9.5; you keep the same capabilities as before.
• Compatibility: You can continue using the SDK with existing integrations without code changes; this release focuses on internal maintenance and stability.

Generated from TemplateFox API v1.9.5

What's New

• Export URL handling: You can now reliably determine how long a PDF export URL remains valid and schedule downloads or refreshes before it expires.
• Bug Fix: Clarify CreatePdfResponse.expires_in description to remove ambiguity and prevent misinterpreting URL lifetime (reduces failed or late downloads).

API Changes

Updated Models:

• CreatePdfResponse - Clarify the expires_in field description (response properties: url, filename, credits_remaining, expires_in). Use expires_in to drive client download/refresh logic.

Generated from TemplateFox API v1.9.4

What's New

• PDF variant clarity: Clarify the pdf_variant field in CreatePdfRequest so you can explicitly choose "pdf/a-2b" or "pdf/a-3b" with guidance on their compatibility and behavioral differences (for example, PDF/A-3b permits embedded file attachments while PDF/A-2b is more broadly supported).
• Better generation outcomes: Help prevent format/validation surprises by making the archival-profile implications of your pdf_variant choice clear when generating PDFs.

API Changes

Updated Models:

• CreatePdfRequest - Update clarifies the pdf_variant property: lists allowed values ("pdf/a-2b", "pdf/a-3b"), explains key differences and impact on output/validation so you can select the correct archival profile for compliance or compatibility.

Generated from TemplateFox API v1.9.3

What's New

• Improved versioning UX: Create version snapshots now require a tag, so you can reliably identify and manage versions (prevents unnamed/ambiguous snapshots).
• Fix: The SDK/API enforces the tag requirement when creating versions, returning a validation error if a tag is missing.

API Changes

Updated Models:

• CreateVersionRequest - The tag property is now required. Include tag (for example "v1.2.0" or "release-2026-04-12") when calling the create-version endpoint; description remains optional.

Generated from TemplateFox API v1.9.0

What's New

• Version management: Update a template version's tag or description reliably; send null in the request to clear a field.
• Bug Fix: Fix critical template versioning bugs that cause updates to fail or unintentionally overwrite fields, so version updates apply consistently.

API Changes

Updated Models:

• UpdateVersionRequest - Request to update a version's tag or description. Now treat explicit null as a command to clear a field and resolve previous failures/overwrites when updating version metadata.

Generated from TemplateFox API v1.8.1