130 results found
-
API: Embedded Signing for Recipient Groups
The feature to support recipient groups with embedded signing.
2 votes -
Receive details of suggestion made via API call/webhook
We generate a document using an API. This means we've created a template that is populated with content via the API. The document is successfully sent to the customer. The customer discovers an error (spelling, numbers swapped, etc.). They can point out this potential error in the PandaDoc web view. Both the sender and the recipient receive this information via email. We would also like to receive this information via the API (status) so that we can directly point it out in our system that populates the documents.
2 votes -
Webhooks: Payment amount and discount percentage can be captured through pricing data configuration in webhook settings.
Hello, when I use the Calculate option when setting up a Payment One time amount equal to say 25% of the total of the Pricing Table, how can I get the paid amount and/or discount amount in webhook notifications?
Currently, when I get a webhook notification when the document changes to a document.paid status, the only amounts that show up are the totals of each pricing table separately and the total of all pricing tables, but no where do I see the paid amount or discount percentage.
Do you have any suggestions?2 votes -
Add Watermark Positioning Controls to PandaDoc
Currently, PandaDoc allows users to customize several watermark properties—such as font size, opacity, text, and color—which is incredibly helpful. However, there is no option to control the positioning of the watermark on the document. This limitation has led to numerous customer complaints, particularly when the watermark obscures critical content like signatures, pricing tables, or legal clauses.
We propose adding a simple yet powerful enhancement: the ability to choose watermark positioning. Even a basic set of options—such as top, bottom, or diagonal—would provide users with the flexibility to ensure watermarks do not interfere with document readability or layout.
Why this matters:
…
2 votes -
Retrieving folder information via API
To be able to use the API's to pull down a list of all of the files in the Content Library for a given workspace.
2 votes -
Payment Gateway: WeTravel Payments via API
Ability to connect WeTravel Payments via API
2 votes -
API Email & Text Sent - If one fails, still deliver by other method.
API - when sending via BOTH email and text, fails if text number invalid. Would like to still send via email when the text option fails.
2 votes -
Ability to mask field tags on PDF documents populated via API
Ability to mask field tags on PDF documents populated via API.
For example, a form where a signer enters their Social Security number. Mask the SSN number for security.2 votes -
Support the "Send via Business Email" feature via API
Support "Send via Business Email" feature via API.
2 votes -
Allow admins to view Remaining API Documents
The ability for admins to view the remaining API documents outside of the Billing tab.
2 votes -
Authentication on the API endpoint that gets called by webhook
Authentication on the API endpoint that gets called by webhook. Currently, PandaDoc webhooks use anonymous "authentication".
2 votes -
Webhook History within the document itself
Be able to see webhooks history within the document itself. And it would be better to have it on the document for easier debugging and replay a webhook.
2 votes -
Ability to manage API developer logs.
Ability to purge API developer logs or set retention period to see only the most recent logs.
2 votes -
[API][Webhook] Pass the ID of the template role in the document requests
It would be great to pass the ID of the template role in the document requests / webhooks (i.e. Recipient completed a document).
2 votes -
Duplicate document via API
Duplicate document via API :
POST /public/v1/documents/duplicate/{id}
Response could be the same as the Create Document from Template
2 votesHi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.
Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!
-
Show section name in the document details request
The ability to see the name of the sections of the pricing table when requesting document details via API.
2 votesHi,
Thank you for taking the time to leave your request. We have great news – the option you are looking for already exists. For more information, please check the link below:
-
Support the X-HTTP-Method-Override header in the API
Please put supporting the X-HTTP-Method-Override header for API on the roadmap. NetSuite is not alone in blocking http PATCH.
We currently have our own integration between NetSuite and PandaDoc. As part of that we need to be able to retire documents when we change an Estimate in NetSuite. At that point the existing document is obsolete. So we are trying to use the api to change the status of the Panda doc from a NS server script:
PATCH https://api.pandadoc.com/public/v1/documents/{document_id}/status/
However PATCH is not universally accepted as a valid HTTP method and the NS scripting api does not offer it. Instead,…
2 votes -
increase document list results
The doc says the Default is 50 and Max is 100. We need more results during the document list API call
2 votesValeryia Baranava responded
-
2 votes
-
2 votes
We wanted to share an update regarding "Get all documents with recipients in one query via API". After careful consideration and further analysis of the idea, we have adjusted its status to "Not Planned."
This change allows us to further explore the feasibility and impact of this and other requested enhancements, ensuring that any updates we introduce are in the best interest of our users and align with our platform's long-term vision.
We appreciate your understanding.
- Don't see your idea?