176 results found
-
Disabling forwarding feature via API.
The ability to disable the forwarding feature via API for all the existing documents and all to come.
3 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, check `forwarding_settings` during Send Document. https://developers.pandadoc.com/reference/send-document#/
-
Password protection via API
The customer would like to use password protection when creating the document via API
3 votesHi,
Thank you for taking the time to leave your request. We have great news – the feature you requested is already available. For more information, please click the link below!
-
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 -
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 -
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 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 -
Support phone-only recipients for embedded signing session endpoint
The ability to use a phone number (E.164 format) in place of an email address in the recipient field of the POST /documents/{id}/session endpoint.
Currently, the endpoint only accepts an email address.
For cases where recipients have no email address on file and the app handles the signing experience directly.
2 votes -
2 votes
-
Public API Endpoint to enable/activate Stripe payments
Request to have a public API endpoint to enable Stripe payments without manually doing it in the UI.
2 votes -
Extend the “Template Updated” webhook trigger to cover updates to templates fields
At the moment, the "Template updated" webhook trigger includes the following events:
Changes to template name
Changes to template roles
Addition of a sectionThe feature request is to extend the “Template Updated” webhook trigger scope to cover updates to templates fields (or possibly introduce a separate trigger "Template updates (fields)".
2 votes -
API: Sender parameter take precedent over owner parameter
If the email specified in the sender parameter does not match an existing workspace user, PandaDoc may automatically assign the document to the default workspace sender. In PandaDoc, the document owner always takes precedence over the sender parameter if the sender does not match the document owner or meet workspace requirements. Even if your API call sets a different sender, the document will still be sent from the document owner.
Would like this to not occur, and allow for the sender perimeter to set the sender email
2 votes -
API Endpoint to Retrieve Workspaces for a Specific User
Request for a new API endpoint that returns all workspaces associated with a specific user within an organization.
Example desired functionality:
GET /users/{user_id}/workspaces
or
GET /user-workspaces?user_id={id}
This would allow integrators to dynamically determine which workspaces a user belongs to without retrieving the full user list across the organization.
Customer Context
Customer operates a franchise model with:
40+ workspaces
500+ users
Shared identity across the organization
Heavy API-based embedded document workflows
Users may belong to multiple workspaces simultaneously.
The customer initiates document creation from their CRM and needs to determine which workspace the user should interact with before creating the document.
…
2 votes