236 results found
-
Add an endpoint to enable retrying webhooks via API
Expected behaviour: we are able to trigger the retry of a failed webhook via an API request.
Example use case: an application site has a period of downtime during which a bunch of webhooks fail to be received and processed. Application admins want to retry all webhooks that failed during the downtime window programmatically.
Manual retrying is time-consuming and prone to errors. Being able to write a script to handle orderly retrying, stale status checking, and recording of the results makes admins more efficient and happier.
8 votes -
API - 1 email to on different roles
Ability to use the same email on different roles in API
3 votes -
In the Document SEND API endpoint,add a new [reply-to] input parameter
In the Document SEND API endpoint, it would be helpful to include a new [reply-to] input parameter, that designates where any potential email response messages goes to. Useful for embedded (and/or whitelabeled) secnarios, where the sender may not be a "real" email address.
4 votes -
Webhook UUID in the payload
Please add "UUID" of the webhook in the webhook payload.
4 votes -
3 votes
-
Ability to manage API developer logs.
Ability to purge API developer logs or set retention period to see only the most recent logs.
2 votes -
[API][Webhook] Pass the ID of the template role in the document requests
It would be great to pass the ID of the template role in the document requests / webhooks (i.e. Recipient completed a document).
2 votes -
4 votes
-
Renewal notifications available via API
Setup renewal notifications via 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
2 votes -
2 votes
-
Contract repository: ability to retrieve data from Data fields via API
Ability to retrieve data from document Data fields via API
2 votes -
Webhook for each time a recipient views a document
Currently PandaDoc only sends a webhook when the document status changes, e.g. from sent to viewed, or viewed to completed. We'd like a webhook to notify our application each time a recipient opens a document. Example use case would be knowing if a recipient has opened a document multiple times and not signed, and we'd like to reach out to them.
2 votes -
Quickbook Online invoicing - percentage per section
Ability to create a single invoice that includes a percentage breakdown, such as invoicing 40% of the labor cost, 100% of the hardware cost, and other sections as needed, all on the same invoice in Quickbooks online
1 vote -
Ability to have more granular options with webhooks
granular with webhooks that they receive with filters (only notified when completed document/PDF available for download)
1 vote -
Duplicate document via API
Duplicate document via API :
POST /public/v1/documents/duplicate/{id}
Response could be the same as the Create Document from Template
1 vote -
[API] Get Org ID
Option to get organization ID via API
2 votes -
2 votes
-
Single Webhook for when document is created
It feels like I have process countless more webhooks just to listen for the creation of a document. This is expensive. I wish there was a way to only receive webhooks on the CREATION of documents so I don't have to process all the webhooks. It saves money.
1 vote -
signer ip address in webhooks
ability to retrieve signers IP address from a webhook
1 vote
- Don't see your idea?