We’ve introduced new endpoint to send email and SMS reminders for documents via the API. This new endpoint allows you to send reminders to all or to some document recipients so that you could manage document follow-ups more flexible and conveniently. Check the Send Manual Reminder in our PandaDoc Public API reference for details.

GET /public/v1/documents/{document_id}/send-reminder

• endpoint added. Attempts to send manual reminders to one or more recipients of a specified document.

We’ve introduced new endpoints to manage auto-reminder settings for documents via the API. These new endpoints allow you to programmatically manage document follow-ups and improve completion rates with more flexibility. Check the Document Auto Reminder Settings, Update Document Auto Reminder Settings and Document Auto-Reminder Settings & Status in our PandaDoc Public API reference for details.

GET /public/v1/documents/{document_id}/auto-reminders

• endpoint added. Retrieve the current auto-reminder settings for a specific document.

PATCH /public/v1/documents/{document_id}/auto-reminders

• endpoint added. Update the auto-reminder settings for a document, including enabling/disabling reminders and customizing reminder schedules.

GET /public/v1/documents/{document_id}/auto-reminders/status

• endpoint added. Check whether auto-reminders are currently enabled or disabled for a document.

Enhanced the Append Content Library Item endpoint with block name mapping functionality:

• Append Content Library Item: Added optional block_mapping property to the response for tracking content block name changes during the append operation.

The block_mapping response includes mappings for content block types (tables, images, and text blocks), showing both the original names from the Content Library Item and their new unique names in the target document. This enhancement enables developers to programmatically reference and manage appended content blocks in subsequent API operations, ensuring accurate block targeting even when name conflicts require automatic renaming.

Example response structure:

{
  "block_mapping": {
    "tables": [
      {
        "original_name": "Products_Table",
        "new_name": "Products_Table_1"
      }
    ],
    "texts": [
      {
        "original_name": "Legal_Disclaimer", 
        "new_name": "Legal_Disclaimer"
      }
    ]
  }
}

This changelog emphasizes the practical value of the feature - solving the problem of tracking content blocks after they've been appended to documents, especially when name conflicts occur and automatic renaming is applied. The feature is particularly valuable for automation workflows that need to reference specific blocks after appending content library items.

POST /public/v1/documents/{id}/append-content-library-item

• added the optional property 'block_mapping' to the response with the '201' status

Enhanced text block functionality with rich content formatting capabilities:

• Create Document: Added optional texts property for specifying text block content during document creation from templates. Supports markdown for rich text formatting.
• Update Document: Added optional texts property for modifying text block content in existing documents. Supports markdown for rich text formatting.
• Document Details: Added texts property to response for retrieving text block names available in the document.

This enhancement allows developers to programmatically manage text blocks with rich markdown content during document creation and updates. Text blocks can now include formatted content such as headings, bold, italic, lists, and links, providing greater control over document presentation and enabling more sophisticated content automation workflows.

POST /public/v1/documents

• added the new optional request property 'texts'

PATCH /public/v1/documents/{id}

• added the new optional request property 'texts'

GET /public/v1/documents/{id}/details

• added the optional property 'texts' to the response with the '200' status

We’ve increased the rate limits for several high-usage Public API operations to support better performance and higher throughput for integrations.

• Create Document from PDF: increased from 100/min to 300/min
• Create Document from Template: increased from 300/min to 500/min
• Get Document Details: increased from 300/min to 600/min
• Download Document: increased from 50/min to 100/min
• Send Document: increased from 200/min to 400/min

These updates help improve throughput and responsiveness for high-volume integrations using the Public API.

We've added a new endpoint to our Public API v2 that allows authorized workspace administrators to retrieve detailed audit trails for their documents.

This new capability helps you programmatically track key events and user actions throughout a document's lifecycle, enhancing transparency and supporting your compliance efforts.

For full technical details on using this endpoint, including parameters and response structures, please see our API documentation: List Document Audit Trail

GET /public/v2/documents/{document_id}/audit-trail

• endpoint added

We have improved the Document Details GET /public/v1/documents/{id}/details endpoint by introducing two new properties: images and tables. These additions provide detailed information about the document's content, enabling more thorough data retrieval.
When you need to update tables and images in a PandaDoc document, you can use the Update Document API. By referencing the table name and/or image name, you can specify exactly which tables or images to update. This ensures precise modifications to the document's content, allowing you to target the correct elements for updates.

You can now programmatically place a notary stamp when creating documents from file uploads—speeding up high-volume notarizations and reducing manual errors. Learn more →

We've completed a major technical refactor to support webhooks for PandaDoc documents notarized via the Notary On Demand service.

To get notified when a document is notarized, simply subscribe to the document_completed_pdf_ready event.

Now with Create DOCX Export Task and DOCX Export Task endpoints you can export PandaDoc document as a DOCX file.

POST /public/beta/documents/{document_id}/docx-export-tasks

• endpoint added

GET /public/beta/documents/{document_id}/docx-export-tasks/{task_id}

• endpoint added