Once a document is created via the API, it is impossible to alter an email address tied to a recipient. In our use cases, it is completely possible that initial email addresses at the time the document is created, have changed before given recipients get around to signing the document.

In PandaDoc API - A way to create a trigger where when a document completes is automatically moves that completed document into a specific folder under their documents

Add possibility to filter by Date Completed and by token value.

https://support.docusign.com/en/guides/ndse-user-guide-manage-automatic-template-matching

https://vimeo.com/370244613

When using only the API to facilitate signers as recipients that do not have official pandadoc accounts, it becomes cumbersome when multiple documents require them to sign. Instead of storing previous signatures that they could use for another, they have to sign for each document. If it was possible to have recipients reuse signatures based on their email, this would significantly improve the ease of use for electronically signing.

The option to set and change expiration date via API.

when using Upload PDF to create PandaDoc via API.

if pdf fails to process we should return useful errors.

Ability to use Embed JS SDK using Pass-though authentication. Giving webapps the ability to allow for their users to create templates without being PandaDcc Users.

No Open API on the customer side

design via API

Have ability to upload images using Editor 2.0 API

API call to create a template.

Create and edit via API

Add an extra status between uploaded in draft to show "Error" state for PDF uploads that fail to process

change document owner in API.