Skip to content

Ideas to Improve PandaDoc

💡 To help us understand (and hopefully implement!) your suggestion, please answer these few questions as you propose your idea:
  • What specific actions or behaviors do you expect from this feature?
  • What is the issue that this functionality would address for you? Why would you require it?

Ideas to Improve PandaDoc

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

276 results found

  1. Currently, the API defaults to a single reminder for sent documents. It would be highly beneficial to allow customization of the number of reminders within the template settings. This would provide greater flexibility for our agents, particularly in cases of email delivery issues or when scheduling callbacks, ensuring better follow-up management.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Currently, it is a limitation of 300 webhooks per workspace. It would be great to increase this number

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. The feature to support recipient groups with embedded signing.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. We generate a document using an API. This means we've created a template that is populated with content via the API. The document is successfully sent to the customer. The customer discovers an error (spelling, numbers swapped, etc.). They can point out this potential error in the PandaDoc web view. Both the sender and the recipient receive this information via email. We would also like to receive this information via the API (status) so that we can directly point it out in our system that populates the documents.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add the ability to view the user who generated each API key directly within the PandaDoc UI for better visibility and audit tracking.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Add the design tab as it is in the regular UI to the embedded editor, so that formatting options such as page number display can be set.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Issue:
    Currently, when adding a new Recipient Group through the PandaDoc API (or manually) with the exact same name as an existing group, the existing group's members are overwritten or updated with the new group's members, instead of creating a distinct new group.

    Impact:
    This behavior causes significant issues and data inconsistencies, particularly when managing recipient groups programmatically via the API, as it leads to unintended changes in existing recipient lists.

    Proposed Idea/Solution:
    Please implement a system that ensures recipient groups with identical names are treated as separate and distinct entities. This could be achieved by:

    Automatically appending a unique…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Hello, when I use the Calculate option when setting up a Payment One time amount equal to say 25% of the total of the Pricing Table, how can I get the paid amount and/or discount amount in webhook notifications?
    Currently, when I get a webhook notification when the document changes to a document.paid status, the only amounts that show up are the totals of each pricing table separately and the total of all pricing tables, but no where do I see the paid amount or discount percentage.
    Do you have any suggestions?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Currently, PandaDoc allows users to customize several watermark properties—such as font size, opacity, text, and color—which is incredibly helpful. However, there is no option to control the positioning of the watermark on the document. This limitation has led to numerous customer complaints, particularly when the watermark obscures critical content like signatures, pricing tables, or legal clauses.

    We propose adding a simple yet powerful enhancement: the ability to choose watermark positioning. Even a basic set of options—such as top, bottom, or diagonal—would provide users with the flexibility to ensure watermarks do not interfere with document readability or layout.

    Why this matters:

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. webhook event for document approved

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Problem

    We need to send quite a lot of information from our webshop to Pandadoc:

    • including short values, like numbers or a couple of symbols
    • but also lists or just formatted text

    This is currently not possible(?) with Pandadoc, as the only way for "dynamic" data are variables. But these are far away from user-friendly...

    • don't allowed formatted text, even not simple one, like strong text.
    • are only really useful for short texts, but we also send paragraphs or long texts.

    → we are currently working with about 100+ variables to be able to have some kind of "decent" layout.…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Introduce a webhook or event trigger that notifies when the signer URL changes due to recipient-forwarding behavior - i.e., when a document is forwarded, the new signer replaces the original, and the signer URL is updated. This would allow clients to keep signer tracking accurate and up-to-date in their systems.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Template Details API is not designed to expose conditional smart content rules or logic, and this is intended behavior. Is there any plan to expose conditional smart content placeholders?

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Ability to create catalog categories from api.
    Right now the only way to create Catalog categories in bulk is by uploading a csv with catalog items which already have a category assigned (along with their sub-categories).
    Would love to do this via api :)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Ability to integrate with OpenSolar API

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. To be able to use the API's to pull down a list of all of the files in the Content Library for a given workspace.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Include the document link in the response body, not just the document ID.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Ability to connect WeTravel Payments via API

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?