266 results found
-
Filter manually completed documents via API call
filter out manually completed documents from the GET documents API call?
3 votes -
Do suggestions via and turn on suggest edits through the API automatically
Do suggestions and turn on suggest edits through the API automatically
3 votes -
End-points for Reports in our public APIs
To be able to Get the total number of the documents within a status ( different statuses) via API
3 votes -
Add an empty value to the content placeholder
Option to add an EMPTY value " " in JSON API to not display any content library from a smart content ? (even if some content library were selected in Pandadoc)
3 votes -
Set up (separate) notifications via API
Option to separate notifications via API. For example, send only PDF of the completed document to the recipient (and not send them "document was sent" notification)
3 votes -
3 votes
-
Ability to create forms via API.
Ability to create forms via API.
3 votes -
API - Ability to Lock documents (content) via API
ability to Locked document feature 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 votes -
3 votes
-
Ignore smart content block if no Content Library items are used when document is created via API.
The option to ignore smart content block if no CLIs are used when document is created via API.
3 votes -
3 votes
-
Improve API to better integrate with Power BI
The ability to integrate the documents response to analytics tool such as power bi dashboard / Enhance the API data to provide the required fields by AWR
3 votes -
API: field tags
To set which from several identical field tags will be populated automatically;
To set date field tag with the date of the opening the document by the client automatically.
3 votes -
API Endpoint to Launch CPQ Workflow.
Would like an API end point to launch a CPQ workflow from Salesforce.
2 votes -
Allow uploading additional files (editable .docx) to an existing document via the Embedded Document Editor
Enable the ability to upload additional files (editable .docx files) to existing documents within the Embedded Document Editor.
2 votes -
[Embedded signing] hide document title / hide language dropdown
At the top of our documents, the name of the document is included twice in the PandaDoc Interface (one row that includes the option to change language, one row that specifies this is document x of y)... and then it's included in our own form itself.
We want to hide one or both of these lines from being displayed. Our application knows if they want the English or the French document, and we only ever include one document to sign at a time.
2 votes -
full-featured support of Quote Builder via API
Sehr geehrtes PandaDoc-Team,
wir nutzen PandaDoc zur automatisierten Angebotserstellung (Trigger aus Pipedrive/n8n, REST-API). Seit Wochen bestehen gravierende Funktionsdefizite, die unsere Angebotsqualität und Conversion direkt schädigen:
Quote-Builder nicht per API nutzbar
– Keine programmgesteuerte Erstellung von Angebotspositionen mit Produktbildern
– Produktkatalog nicht sauber per API abrufbar/zu verknüpfen
– Folge: Angebote ohne positionsgenaue Bilder, teils graue Platzhalter („grey image placeholder“)
Fehlende vollständige DE-Lokalisierung
– Feste Spaltenbezeichner wie „Quantity“/„Price“ in Angeboten und Systemoberflächen
– Nicht überall über Templates übersetzbar → Vertrauensverlust bei B2B- und Privatkunden
Instabiles Bild-Rendering via API
– Bildfelder in Vorlagen werden via API nicht zuverlässig gefüllt; Layout bricht oder zeigt…2 votes -
Update Signing Order once document is sent via API
when I try using the endpoint and passing in a signing_order I do not see it reflected on the recipient. Being able to change the signing order programmatically is something that is important to us since, per our last call, we have decided that we are going to be hiding the recipients option and building our own custom recipients UI
2 votes -
To have more then 300 webhooks per workspace
Currently, it is a limitation of 300 webhooks per workspace. It would be great to increase this number
2 votes
- Don't see your idea?