176 results found
-
Failure Notification email setup
To include Failure Notification email setup
1 vote -
When posting, it helps to include: A clear title (e.g., “Allow adjustable transparency for email background color”) Your use case Current li
Allow adjustable transparency for email background color
Current limitation (no fade control)
Expected behavior (user-controlled opacity)
Branding is a must-colors are direct source of placement and this is too easy to make happen. You can create smooth color fade changes using CSS Transitions for interactive elements or CSS Gradients for static transitions.1 vote -
Ability to set the position of the bundled document when adding it via API call
At this point, when adding bundled document via /sections/uploads, it always appears at the end of the initial document.
It would be great to have the parameters such as order or position to control the location of the newly added document (i.e. if I set up "bundle_position": "0", the system will add my document to the very beginning).
2 votes -
Export Document Data: API
Not really. i know i can export the data to csv however, i am automating the extraction process by using the API key to call the data into another system where i can use it for reporting. The production API pulls tokens, variables and some fields from documents but it does not pull data manually entered into the "Review Data" form. this is the challenge. How can the API pull that manually entered data? see the screenshot i sent to you earlier.
2 votes -
API endpoint to delete a single Collect Files upload without deleting the whole document
There's currently no API endpoint to remove just a Collect Files field's uploaded file from a Completed document — the only option is deleting the entire document via the API, which also removes its PDF, certificate, and audit trail. Customers using Collect Files for identity verification need a way to purge just that file after a retention period (e.g., 180 days) while keeping the document itself intact.
2 votes -
Allow updating contract metadata via API for imported/completed documents
We bulk-imported our legacy contracts into PandaDoc's Contract Repository and need to add metadata (partner, start date, end date, etc.) to them in bulk via API, so our team can search, filter, and report on this data. Right now this can only be done manually, one document at a time, through the editor's Data panel. Please add API support for writing Contract Repository metadata fields on documents, including ones that are already completed, so bulk-imported contract archives can be populated without manual data entry.
2 votes -
Fix API text rendering to prevent text overlap with invisible field tags
Problem:
When PDFs with invisible (white-colored) embedded text containing PandaDoc Field Tags are uploaded via the API, the form text gets cut off or overlaid by the field tags. The same PDFs upload correctly via the UI with no text issues.
Customer Impact: Forms created through the API are incomplete and unusable for signing—critical information is hidden.
Feature request: Fix the API's PDF text rendering to match the UI behavior—ensure invisible field tags don't cause text overlap regardless of upload method.
2 votes -
Include document type in webhook payload
Include the document type in webhook payload so that this can be used for automations and workflows.
1 vote -
Add catalog images to the pricing table via API
I want to add the products in a table that can then be selected or deselected but I want the catalogue images to be populated in there
2 votes -
Allow users to configure the "next" button on the template level for signers via API
We often have issues where clients send a document to someone to sign and a number of non-required fields are missed. When the signers use the "next" button, it jumps from one required field to the next, meaning intermediate non-required, but important fields are missed.
1 vote -
Fix field-tags docs: examples show square brackets, but only curly braces parse
The docs page https://developers.pandadoc.com/docs/field-tags shows square-bracket
examples like [textfield:user:name], but the API only recognizes curly-brace
tags ({textfield:user:name}). Support chat confirmed curly is the correct
syntax. Two asks:- Update every example on that page to curly braces.
- Make unparseable/bracket-style tags return a validation warning instead of a silent no-op — today the doc uploads fine with zero fields and recipients silently degrade from signer to CC, which you don't notice until someone can't sign.
1 vote -
Silent Document Ownership Transfer via API
Add an option to transfer document ownership via API without sending an email notification to the new owner.
2 votes -
extend recipient view audit log to include all views, not just the first
extend recipient view audit log to include all views, not just the first
this would be required for a security access audit on the document, controls need to exist to show details about every view
2 votes -
add audit trail entries for internal users that access/open a document
add audit trail entries for internal users that access/open a document
even after a document is signed, for security access control audits
2 votes -
in the document details endpoint, for each recipient, add the number of views that recipient has had on the underlying document
in the document details endpoint, for each recipient, add the number of views that recipient has had on the underlying document
2 votes -
API: Auto-convert uploaded DOCX documents to editable format without requiring manual UI action
When a DOCX file is uploaded via the PandaDoc API, it remains static and read-only by default, and the "Make editable" conversion currently requires a user to manually open the document in the editor UI.
2 votes -
Add ‘Rejected’ status to reporting and CSV exports
Currently, reporting and CSV exports include statuses like Draft, Sent, Viewed, Completed, Expired, and Declined, but there is no way to see a global count of documents that were rejected in the approval workflow.
“Rejected” exists as a document status in the API, but it is not available in reporting dashboards or exported analytics files.
Request: Add a Rejected status tile in reporting and include it in the CSV export so teams can track this metric across all documents.
1 vote -
Add section_uuid to pricing table objects in webhook and document details API
When a bundle document is signed, the recipientcompleted webhook returns pricing.tables[] with no reference to which section each table belongs to. The same gap exists in GET /documents/{id}/details. There's currently no way to cross-reference pricing tables back to their originating bundle section via the API.
Request: Add a sectionuuid field to each pricing table object in:recipientcompleted webhook — pricing.tables[].sectionuuid
GET /public/v1/documents/{id}/details — pricing.tables[].section_uuid2 votes -
Preview should not generate a document or consume credits
When I select 'preview' on a form under the templates tab, it creates a new form, which is then deducted from my usage credits -- this is deceptive, as a preview shouldn't create a new form. A preview -- by description -- is supposed to show you what the page will look like when active, but not be active itself.
The usage credits are very expensive, so you need to warn people in advance that you can't preview a form without creating one, and that it will cost you a credit. I've wasted a bunch of credits on this, when…1 vote -
Room-related webhook events (such as room.created, room.viewed, etc.)
Function that would allow customers to detect Room activity via the API and connect it to their CRM data.
6 votes