New

DocSpring now has an official Zapier integration.

Our integration includes:

• Prebuilt triggers: submission processed, submission failed, data request completed, and more
• Actions like Generate PDF and Combine PDFs, with your template's fields already mapped as inputs
• Searches to look up a template or a submission

Our Zapier app is currently private, and we need a few more users to try it out before we can publish it. If you're interested in trying out the integration, you can visit the following URL:

https://zapier.com/developer/public-invite/71146/b6aae75c1a0ee6197d29f61f39c5a782/

Please email support@docspring.com if you have any feedback or feature requests!

Improvement

DocSpring has a new webhook system:

In previous versions of DocSpring, you could configure webhook URLs for each template or API token. These webhook URL fields have now been removed from the template settings and API token edit form. Instead, you can configure "Scopes" to only send a webhook for certain API tokens, templates, or folders:

We now support sending webhooks for many more kinds of events, including submissions, data requests, templates, folders, users, and many other resources.

We have migrated all existing template and API token webhooks to our new webhook system. All migrated webhooks will continue sending the same payloads as before (our legacy v2 version). Newly created webhooks will be on v3 by default which has a much better and more consistent payload. We also include a signature header that you can use to verify that the webhook was sent by DocSpring.

We will automatically disable webhooks after they have been failing for 3 days. We will send you a notification if a webhook starts failing, and another notification after 1 day of failures.

Please let us know if you have any questions or feedback about our new webhook system.

Improvement

We've just rolled out some major improvements to our HTML-to-PDF rendering pipeline, so rendering PDFs will be faster, more reliable, and more secure. We can now run many more HTML-to-PDF jobs in parallel, so large submission batches should complete much more quickly.

We have carefully tested these changes before rolling them out and are closely monitoring our metrics and logs. Please contact support if you notice any issues with HTML templates.

Improvement

We've released some improvements to the template editor.

Select Multiple Fields

You can now select multiple fields and move or edit them as a group.

Use the new "Select" tool at the top left:

Field Snapping

We've added field "snapping" so you can align fields with other fields. This can be toggled on or off via the magnet button at the top left.

Double Click to Edit Name

You can now double-click to edit a field name in the left sidebar.

Please let us know if you have any questions or feedback.

New

You can now embed the DocSpring template editor directly inside your own application.

This is useful when your users need to configure PDF templates, place fields, and publish template changes without switching over to the DocSpring dashboard.

How It Works

Add template_editor.js to your page, then open the editor inline or as a modal:

<script
  type="text/javascript"
  src="https://cdn.docspring.com/embed/template_editor.v0.1.0.js"
></script>

<div id="template-editor" style="height: 720px"></div>

<script>
  DocSpring.createTemplateEditor('#template-editor', {
    templateId: 'tpl_123',
    token: 'EMBED_EDIT_TOKEN',
    inline: true,
    externalUser: {
      name: 'Jane Editor',
      email: 'jane@example.com',
      external_id: 'user_123'
    },
    onDone: function(data) {
      // Close your modal or move to the next step in your app.
    }
  })
</script>

The embedded editor always edits the draft template. If versioning is enabled for the embedded editor, users can publish, restore, and delete published versions from inside the editor.

Highlights

• Inline or Modal Embed the editor inside a page, or open it in a modal with one JavaScript call.

• Customizable UI Show or hide specific controls with feature options. You can simplify the editor, customize the Done button, force light or dark mode, adjust modal sizing, and control whether settings, versioning, document replacement, schema links, form links, help, and advanced field options are visible.

• Predefined Fields You can provide a controlled list of field names and data types with predefined_fields. Users can drag predefined fields onto the template.

• Required Predefined Fields Mark predefined fields as required_in_template when they must be added before the user can finish. This is separate from field_required, which controls whether submitted data must include a value for that field.

• External User Attribution Pass externalUser details from your app so template changes and published versions show the correct editor name, email, and external user ID. If no user details are provided, changes are attributed to Embedded Template User.

• Server-Enforced Permissions Embedded users can edit template fields by default, but sensitive capabilities are disabled unless you explicitly enable them on the template:

  • embed_edit_allow_settings
  • embed_edit_allow_versioning
  • embed_edit_allow_document_replacement

  When settings access is disabled, sensitive settings such as webhook URLs, redirect URLs, Slack webhook URLs, and PDF encryption passwords are hidden from the embedded editor.

Try It

You can test the embedded template editor here:

https://docspring.com/embed_template_editor_example

You will need a template UID and an embed edit token. You can find the embed edit token on the template settings page.

Documentation

See the full guides here:

• Embed the Template Editor
• Customize the Embedded Template Editor
• Use Predefined Fields

If you have any questions or feedback, please contact support.

Improvement

DocSpring now supports dark mode:

You can change the theme at the bottom-right corner of most pages:

When the dark mode theme is active, an "Invert" button will be shown in the PDF template editor. This will flip the colors of the PDF pages, so that black text on a white background will become white text on a black background.

Please note that "Invert" mode only applies to the pages that are displayed in the PDF template editor. It does not affect generated PDFs.

Dark mode support has also been added to our hosted web forms:

However, it is not yet available on embedded data requests or visual forms. Please let us know if you need more theming options for embedded forms.

New

We've added a new field type for initials:

These are very similar to signature fields and share the same API schema.

If you use our Data Requests JavaScript library then you don't need to make any changes. If you use our low-level Visual Forms library, support for this new field type has been released in version 2.7.2.

New

DocSpring is proud to announce our achievement of SOC 2 Type II certification. This milestone highlights our focus on data security and reaffirms our commitment to upholding rigorous standards in protecting customer information.

We extend our sincere appreciation to the team at Comp AI for their invaluable guidance and expertise, which were instrumental in reaching this significant milestone.

Improvement

We've rebuilt the DocSpring documentation site. Our new docs are split up into three main sections:

Documentation

DocSpring features and reference pages

Guides

Step-by-step instructions for working with our embedded libraries and setting up integrations

API Reference

A complete API reference including code examples for all of our API client libraries. (100% end-to-end tested!)

Our new docs are built using Astro, Starlight, and Scalar. Many thanks to the amazing teams behind these open source projects!

New

We’re excited to announce that DocSpring now supports Template Versioning!

This update allows you to maintain multiple template versions (e.g., 1.2.3) and manage a safe “draft” vs. “production” workflow, so you can make changes to your templates without breaking any existing integrations.

Highlights

• Draft vs. Published Versions
  Each template now supports a “draft” version for in-progress changes, as well as published versions that you can refer to in your existing code or API integrations.

• Semantic Versioning (major.minor.patch)
  Templates support version strings like 1.2.3. You can automatically increment version numbers when publishing new changes. We recommend incrementing minor and/or patch for backwards compatible changes, and major for breaking changes (e.g. new required fields, or changes to the PDF.)

• API Support

  • Generate Submission: Accepts an optional version parameter (e.g. 1.2.3, draft, or latest). The API will use the latest published version by default, or the draft template if no versions have been published.
  • Publish & Restore Template Versions: New endpoints to manage template versions. Publish a new version, or restore a published version to the draft.
  • Copy / Delete: These existing API endpoints now support versioning, including partial version strings. You can now duplicate a published template version to create a new draft template. You can also delete specific template versions.

• Audit Trails & Submissions
  Submissions now store the exact template version that generated them. You can see this version in the Submission pages, letting you track precisely which version was used.

• Reprocessing Submissions
  We have redesigned the "reprocess" button to open a form that allows you to select a specific template version. You can resubmit submission data to fill out the latest published template, the draft template, or a specific version.

• UI Updates

  • Versions Tab: A new “Versions” link in the template dropdown menu opens a Versions modal.
  • Locked Templates: Instead of the blocking “locked” modal, we now display a version badge in the header. You can now easily lock and unlock templates by visiting the template settings.

Getting Started

• Publish a Version
  
  1. Make changes to your draft in the Template Editor.
  2. Open the Versions modal and click the “Publish version” button to open the "New Version" form.

3. Enter an optional description for the new version and choose which version number to increment: "major" (v1.0.0), "minor" (v0.1.0), or "patch" (v0.0.1). You can also publish a new version via the API (see docs for details).

• Use a Specific Version in Your Integration

  POST /api/v1/templates/<TEMPLATE_ID>/submissions
  {
    "version": "1.0.0",
    "data": { ... }
  }

If you omit version, we’ll automatically use the latest published version, or the draft if none are published. You can also specify a partial version (e.g. 1.0 or 1), and this will find the latest matching version. Other possible values are: draft, and latest.

• Restore or Copy an Older Version
  
  • Click “Restore to Draft” in the UI or use the new “restore version” API endpoint to roll back your template to a previous version.
  • Or you can copy an older version to a brand-new draft, preserving the original as-is.

View Changes Between Templates

When publishing a new version, you can see how many fields or settings have been changed in the draft template:

You can click this text to view the full details.

There is also a "Show Changes" link in the dropdown menu for each version.

View Older Versions

You can view an older version by clicking on the row in the versions table. Published versions cannot be modified, so this will load a read-only version of the template editor. You can click on fields to view their properties, or open the Settings page to view template settings.

Documentation

See detailed API examples in our API Reference Docs.

All of our API client libraries have been updated to support the new template version parameters. Here are the latest versions:

• C#: DocSpring.Client v3.1.0
• Elixir: docspring v2.1.0
• Go: docspring-go v2.1.0
• Java: DocSpring v2.1.0
• JavaScript: docspring v2.1.0
• PHP: docspring v2.1.0
• Python: docspring v2.1.0
• Ruby: docspring v3.1.0
• TypeScript: docspring-ts v2.1.0

If you have any questions or feedback, reach out to our support team.