124 results found
-
Embedded Editor: support Card details field
Option to support the Card details field when using Embedded Editor (API).
3 votes -
Update Signing order via API
We would to be able to use the API to change the signing order for any document so that we can adjust the order in which customers sign documents.
3 votes -
API: redirect to a custom URL in a session view
API: redirect to a custom URL in a session view.
3 votes -
Ability to remove Space if no variables is passed
The Ability to remove the empty spacing if no variable is passed.
Example: Not all have a 2nd address and if none was placed it will leave a blank, instead of a Blank space. To just add a custom spacing of pull in the next set of variables inline with the Template
3 votes -
Add a new API to fetch the ip-address (and geo location tags) of all Document signatures
As part of fraud detection measures, a PandaDoc client may want to parse the source ip-address (and geo-location tag) of all document signatures and run them through a fraud-detection service to see if any red flags are raised that need further investigation.
3 votes -
API - 1 email to on different roles
Ability to use the same email on different roles in API
3 votes -
Document deletion via API: keep the document in trash folder
Currently, when a document is deleted via API, it is deleted permanently. Have an option to have a document in the trash folder in case it was deleted via API
3 votes -
Upload image or photos in collect files field using API
to be able to upload an image or photo in the collect files fields using API
3 votes -
API: Add pages to a document
Currently, we can bundle documents via API but not add documents as pages.
3 votes -
Add endpoint to share templates via API
Add endpoint to share templates via API
3 votes -
Option to enable multiline via API / Make
- Will allow the user to enable multiline text in API or Make
3 votes -
API: nested fields in body request
Option to use nested fields in the body request when you create a document from PandaDoc template via API
3 votes -
GET Documents by Sequence Number
Currently in Zapier and in the API documentation it says you can find documents via Sequence Numbers, but this is not the case. It would be incredibly useful to GET documents via API with a unique identifier such as Sequence Numbers. This way we can make a connection between Apps to find PandaDoc documents and associate them to other apps via automations.
3 votesValeryia Baranava responded
-
3 votes
-
3 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 -
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.
2 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
- Don't see your idea?