136 results found
-
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 -
Export All Catalog Items via the API
Currently, users are using the existing “List Catalog Items Search” endpoint to retrieve and export all catalog items via the API. However, this endpoint was originally designed as a search endpoint, intended to filter a relatively small subset of items based on a specific query. It was not built to reliably return the entire catalog, which can lead to limitations and unintended errors when used as a full listing mechanism.
2 votes -
Allow uploaded .DOCX files to be editable using https://www.npmjs.com/package/pandadoc-editor
It's currently not possible to make uploaded .docx file editable using the PandaDoc Editor NPM Library: https://www.npmjs.com/package/pandadoc-editor
We would like it to work the same way as within the native PandaDoc application.
we should be able to make .docx files editable using this NPM Library2 votes -
2 votes
-
For the 'Catalog item details' API request to return product's subcategory.
For the 'Catalog item details' API request to return product's subcategory.
2 votes -
A way to "escape" the interpretation of square brackets ([]) as Variables via the API
The ability to "escape" the interpretation of square brackets ([]) as Variables via the API.
2 votes -
Option to Set Fields as “Required by Default” in the Embedded Editor
Ability to configure whether fields added in the embedded editor are required by default (or have an option to toggle this behavior).
2 votes -
API: leave the smart content block in place, and a user can select content from the pre-selected items after the document is generated, befo
You cannot currently create a document via the API and leave the smart content block in a “pending selection” mode (i.e., so the user can later choose from the pre-selected content in the UI) in the exact same way as you can in the Editor. When using the API, you must specify which content library item(s) to insert into each smart content block at the time of document creation, or make the block optional (which means it can be empty in the generated document). The API does not support leaving the smart content block in the same “interactive, user-selectable” state…
2 votes
- Don't see your idea?