Merge Field is a field property that allows to link fields when their values are set via API, similar to how Field Id works on the UI.

You can set the field value during document or section creation from a template, referring to fields by their Merge Field property, see instructions: Prefilled fields .

Now, you can control how merge fields behave in a bundle when adding a new section from a template . Set the merge_field_scope query parameter:

• document (default) leaves the Merge Field properties untouched. Field values with the same Merge Field name will override field values of the whole document.
• upload adds a unique suffix to all the Merge Field names added in scope of this operation. Use it if you add one template multiple times to the same bundle, but don’t want the fields to be syncronized.

🚧

This functionality is in beta

While we are improving this functionality, the implementation details can be changed without notice.

With the new Document Fields endpoints, you can get fields configuration for an already created document and replicate it on a new document, or place a field at specific coordinates. Take a look at the methods reference:

1. [Beta] List Document Fields
2. [Beta] Create Document Fields

As an organization admin, you can now Add Member to Workspace via API.

Now you have the option to redirect the signer to a different URL after the document is signed or paid. Learn more: Redirect to a URL upon completion .

As an organization admin, you can now create a user via API and assign them a role, a license, and a workspace or several.

After a document is created, you can set up verification for the document recipient, either via passcode or a one-time password delivered via SMS. Learn more: Enable recipient verification.

With the new Update Quote endpoint, you can use data from any external catalog to update a quote in your PandaDoc document. Watch the demo: Update Quotes.

You can now track template changes in an effective way with these enhancements:

1. The template_created webhook triggers on template creation.
2. The template_updated webhook triggers on these changes to a template:
   1. A role added or deleted.
   2. Template renamed.
   3. A section added to a content bundle.
      See the full webhook events list: Webhook Payload.
3. An optional fields=content_date_modified query parameter for List Templates shows the timestamp for the latest change to template content.

Now Document Details reflects whether a quote section or an entire quote is optional or selected.

Look for these groups in the responses: "quotes" -> "settings" and "quotes" -> "sections" -> "settings":

"settings": {
              "optional": true,
              "selected": true,
              "selection_type": "custom"
            }

There are three selection types available:

1. Single: You can only select one item. Applied to all items in a section or a quote.
2. Multiple: You can select several items. Applied to all items in a section or a quote.
3. Custom: Applied to several (but not all) items inside a section or a quote.

Now, you can send PandaDoc documents, collect signatures, gather customer data, and manage your document workflow via text (SMS) messaging.

This update introduces two significant enhancements to PandaDoc API:

1. Delivery Options: With the introduction of the delivery_methods parameter, you have the power to choose how your recipients receive their documents.
2. Optional Email Field: We've made the email field optional when creating or updating contacts and recipients, giving you more flexibility in your workflows.

🚧

Important

If you're considering SMS delivery, review your setup. Changes may affect your workflow, especially if you rely on email as a required field. If the email is not set for a recipient or contact, the email field returns null in the webhook response, potentially affecting your workflow.

If you don't plan on using recipients or contacts without an email, your workflow will remain unchanged.

Delivery Methods

To update the delivery method for any recipient, use the Update Recipient endpoint. Specify the delivery_methods parameter by choosing between email, sms, or both.

{
  ...,
  "delivery_methods": {
    "sms": true,
    "email": false,
  }
}

If you plan to send a document via SMS, provide the recipient's phone number in an international format with the country code (for example, +12025551234).

If you haven't provided a phone number or have provided it in the wrong format, you will receive a 400 Bad Request error when trying to send a document via the Send Document endpoint.

You can retrieve the existing delivery methods for each recipient via the Document Details endpoint.

Non-mandatory email

The email field is now not required to create and update contacts and recipients.

Changes by API endpoint