136 results found

1. Show section name in the document details request

   The ability to see the name of the sections of the pricing table when requesting document details via API.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Solution Exists  ·  AdminDaria Serebriakova (Product Ops Specialist, PandaDoc) responded

   Hi,

   Thank you for taking the time to leave your request. We have great news – the option you are looking for already exists. For more information, please check the link below:

   Document Details

2. Support the X-HTTP-Method-Override header in the API

   Please put supporting the X-HTTP-Method-Override header for API on the roadmap. NetSuite is not alone in blocking http PATCH.

   We currently have our own integration between NetSuite and PandaDoc. As part of that we need to be able to retire documents when we change an Estimate in NetSuite. At that point the existing document is obsolete. So we are trying to use the api to change the status of the Panda doc from a NS server script:

   PATCH https://api.pandadoc.com/public/v1/documents/{document_id}/status/

   However PATCH is not universally accepted as a valid HTTP method and the NS scripting api does not offer it. Instead, to do a PATCH from NS, we usually use the standard workaround which is a POST with a header 'X-HTTP-Method-Override' = 'PATCH'

   When we do this, we get an error because it is not supported by your API.

   Please put supporting the X-HTTP-Method-Override header for API on the roadmap. NetSuite is not alone in blocking http PATCH.

   We currently have our own integration between NetSuite and PandaDoc. As part of that we need to be able to retire documents when we change an Estimate in NetSuite. At that point the existing document is obsolete. So we are trying to use the api to change the status of the Panda doc from a NS server script:

   PATCH https://api.pandadoc.com/public/v1/documents/{document_id}/status/

   However PATCH is not universally accepted as a valid HTTP method and the NS scripting api does not offer it. Instead,… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. increase document list results

   The doc says the Default is 50 and Max is 100. We need more results during the document list API call

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Valeryia Baranava responded

4. set document currency via api
   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Valeryia Baranava responded

5. To get all documents with recipients in one query via API
   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Not Planned  ·  AdminSergei Soroka (Admin, PandaDoc) responded

   We wanted to share an update regarding "Get all documents with recipients in one query via API". After careful consideration and further analysis of the idea, we have adjusted its status to "Not Planned."

   This change allows us to further explore the feasibility and impact of this and other requested enhancements, ensuring that any updates we introduce are in the best interest of our users and align with our platform's long-term vision.

   We appreciate your understanding.

6. Use API to integate Pipedrive with PandaDoc

   To be specific, I'm using Pipedrive as my CRM which integrates with Pandadoc. My question relates to using the API to make that connection and not have to manually login to make the connection.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Maintain Hubspot Deals card by migrating to Hubspot App Cards

   I went to use Panda from within Hubspot Deals today and got this message (see pic)

   What specific actions or behaviors do you expect from this feature?
   Maintain existing feature set

   What is the issue that this functionality would address for you? Why would you require it?
   Our contract eSign is built around it. We were about to upgrade to build our entire eSign around it but won't be able to do so if this update is not implemented.

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Allow users to configure the "next" button on the template level for signers via API

   We often have issues where clients send a document to someone to sign and a number of non-required fields are missed. When the signers use the "next" button, it jumps from one required field to the next, meaning intermediate non-required, but important fields are missed.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Fix field-tags docs: examples show square brackets, but only curly braces parse

   The docs page https://developers.pandadoc.com/docs/field-tags shows square-bracket
   examples like [textfield:user:name], but the API only recognizes curly-brace
   tags ({textfield:user:name}). Support chat confirmed curly is the correct
   syntax. Two asks:

   1. Update every example on that page to curly braces.
   2. Make unparseable/bracket-style tags return a validation warning instead of a silent no-op — today the doc uploads fine with zero fields and recipients silently degrade from signer to CC, which you don't notice until someone can't sign.
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add ‘Rejected’ status to reporting and CSV exports

    Currently, reporting and CSV exports include statuses like Draft, Sent, Viewed, Completed, Expired, and Declined, but there is no way to see a global count of documents that were rejected in the approval workflow.

    “Rejected” exists as a document status in the API, but it is not available in reporting dashboards or exported analytics files.

    Request: Add a Rejected status tile in reporting and include it in the CSV export so teams can track this metric across all documents.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Preview should not generate a document or consume credits

    When I select 'preview' on a form under the templates tab, it creates a new form, which is then deducted from my usage credits -- this is deceptive, as a preview shouldn't create a new form. A preview -- by description -- is supposed to show you what the page will look like when active, but not be active itself.
    The usage credits are very expensive, so you need to warn people in advance that you can't preview a form without creating one, and that it will cost you a credit. I've wasted a bunch of credits on this, when we don't have extra to spare.

    When I select 'preview' on a form under the templates tab, it creates a new form, which is then deducted from my usage credits -- this is deceptive, as a preview shouldn't create a new form. A preview -- by description -- is supposed to show you what the page will look like when active, but not be active itself.
    The usage credits are very expensive, so you need to warn people in advance that you can't preview a form without creating one, and that it will cost you a credit. I've wasted a bunch of credits on this, when… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Bulk Refresh/Update of Salesforce Fields Across All Workspace Templates

    Currently, when changes are made to Salesforce object schemas (such as field renames, new custom fields, or mapping updates), or when fields simply need to be resynced, administrators must manually open every single template in a workspace to refresh or update the Salesforce tokens/fields. For workspaces with dozens or hundreds of templates, this manual process is incredibly tedious, prone to human error, and a major operational bottleneck.

    Proposed Solution
    We need a way to trigger a bulk refresh of Salesforce field mappings for all templates within a specific workspace simultaneously. This could be achieved via two proposed methods:

    Option A (UI-Based): A "Bulk Refresh Salesforce Fields" button located within the Workspace Settings (under Integrations > Salesforce) or on the Templates dashboard.

    Option B (API-Based): A dedicated API endpoint (e.g., POST /v1/workspaces/{id}/templates/salesforce/refresh) that allows developers to programmatically trigger this sync.

    User Story
    As a PandaDoc Workspace Administrator,
    I want to trigger a single action to update Salesforce fields across all my templates at once,
    So that I don’t have to manually open and update 100+ templates every time our Salesforce architecture evolves.

    Performance & Technical Expectations
    Asynchronous Processing: We understand that bulk updating fields across many documents can be resource-intensive. This action can run as a background job (asynchronous process) with a status indicator (e.g., "Syncing...").

    SLA / Time Constraint: Execution speed is not critical. A background queue processing time of up to 1 hour per 100 templates is perfectly acceptable, as long as it requires zero manual intervention once triggered.

    Error Reporting: A simple summary log or notification upon completion indicating if any templates failed to sync (e.g., due to a deleted field in Salesforce).

    Business Value / Impact
    Time Savings: Saves hours of administrative grunt work whenever Salesforce fields are updated.

    Data Integrity: Ensures that all generated documents are pulling from the correct, updated Salesforce fields without relying on admins remembering to update every single template.

    Scalability: Allows enterprise teams to confidently scale their template libraries past 50+ templates without fearing the maintenance overhead.

    Currently, when changes are made to Salesforce object schemas (such as field renames, new custom fields, or mapping updates), or when fields simply need to be resynced, administrators must manually open every single template in a workspace to refresh or update the Salesforce tokens/fields. For workspaces with dozens or hundreds of templates, this manual process is incredibly tedious, prone to human error, and a major operational bottleneck.

    Proposed Solution
    We need a way to trigger a bulk refresh of Salesforce field mappings for all templates within a specific workspace simultaneously. This could be achieved via two proposed methods:

    Option A… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Custom Product Image through API

    We have a Shopify website that allows customers to upload a reference image showing how they would like their product to be customized.

    As the contract is generated automatically through the API without any manual intervention, we would like this uploaded reference image to be displayed in the pricing table. Including the image would provide clear visual context for the customized product and help avoid any ambiguity.

    In scenarios where a customer uploads a reference image, our system creates a custom product via the API. However, we are currently facing a limitation in assigning the uploaded image to the custom product in a way that allows it to appear in the pricing table.

    Could you please advise if there is a supported approach or best practice to associate the uploaded image with the custom product so that it is displayed in the pricing table generated through the API?

    We have a Shopify website that allows customers to upload a reference image showing how they would like their product to be customized.

    As the contract is generated automatically through the API without any manual intervention, we would like this uploaded reference image to be displayed in the pricing table. Including the image would provide clear visual context for the customized product and help avoid any ambiguity.

    In scenarios where a customer uploads a reference image, our system creates a custom product via the API. However, we are currently facing a limitation in assigning the uploaded image to the custom… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Slide show of multiple images in a document

    Ability to add a slide show of multiple images in a document

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Org-level API endpoint to retrieve workspace membership by user

    Customer is requesting improvements to multi-workspace API architecture for Enterprise franchise use cases.

    Current customer environment:

    40+ franchise offices
    Each franchise requires its own PandaDoc workspace
    Users may belong to multiple workspaces
    CRM + embedded signing workflow is the primary use case
    PandaDoc is being used primarily as an API-driven signing/orchestration layer

    Current pain points:

    Workspace API keys are isolated per workspace
    Customer must maintain:
    workspace API keys
    workspace/user mappings
    webhook management per workspace
    synchronization logic internally
    No efficient org-level way to dynamically determine which workspaces a specific user belongs to

    Main customer request:

    Org-level API endpoint to retrieve workspace membership by user
    Example desired functionality:
    "Get all workspaces this user belongs to"
    Customer wants to dynamically route users into the correct workspace during embedded signing/document workflows

    Customer is Insureline

    Customer is requesting improvements to multi-workspace API architecture for Enterprise franchise use cases.

    Current customer environment:

    40+ franchise offices
    Each franchise requires its own PandaDoc workspace
    Users may belong to multiple workspaces
    CRM + embedded signing workflow is the primary use case
    PandaDoc is being used primarily as an API-driven signing/orchestration layer

    Current pain points:

    Workspace API keys are isolated per workspace
    Customer must maintain:
    workspace API keys
    workspace/user mappings
    webhook management per workspace
    synchronization logic internally
    No efficient org-level way to dynamically determine which workspaces a specific user belongs to

    Main customer request:

    Org-level API endpoint to retrieve workspace… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. API: Track individual field completion or real-time page navigation

    Create an API endpoint or webhook that triggers based on individual field completion or real-time page navigation.

    we're looking for some way of better tracking how far along someone's getting with a document. Right now it's split into 10 key requirements, so we thought maybe that's a better way of tracking progress within a document

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. filter webhook history in the PandaDoc Developer Center using a custom date range

    It would be great to have the ability to filter webhook history in the PandaDoc Developer Center using a custom date range, in addition to the existing preset options. This feature would make it easier to review and analyze webhook events for specific periods.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. API Key deactivation prompt when a user is removed (API Key user-generated)

    A notification or prompt that the APIK key needs to be reset if the user who generated is removed.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. pass custom parameters to the redirect url

    Today, the Redirect URL after completion setting appears to be static. It would be extremely valuable if this redirect could be dynamically customized per document/session via integrations (e.g., Make / Zapier) or via variables, so customers can redirect signers to different landing pages and pass custom query parameters.

    Why this matters (use case):

    We run multiple campaigns and need to send signers to different LPs depending on:

    document template / campaign

    recipient / segment

    region / language

    deal owner / pipeline stage

    We also want to pass tracking parameters such as:

    utmsource, utmcampaign, utm_content

    internal IDs like docid, recipientid, deal_id

    This would unlock cleaner attribution and better post-sign flows (e.g., showing different onboarding steps).

    Proposed solution:
    Enable the redirect URL to be set programmatically (API + Make/Zapier) and/or with merge fields / variables, for example:

    https://example.com/thank-you?doc={{document.id}}&email={{recipient.email}}&campaign={{custom.campaign}}

    Acceptance criteria:

    Redirect URL can be set/overwritten when creating a document from a template (API / integration step).

    Redirect URL supports variables/merge fields and/or payload-based parameters.

    Redirect URL can be different per recipient (optional but ideal).

    Secure handling of parameters (e.g., allowlist / encoding) to avoid injection issues.

    Works for completed signing events consistently (web + mobile).

    Expected impact:

    Better conversion tracking and attribution

    More flexible campaign routing

    Stronger automation use cases with Make/Zapier

    Today, the Redirect URL after completion setting appears to be static. It would be extremely valuable if this redirect could be dynamically customized per document/session via integrations (e.g., Make / Zapier) or via variables, so customers can redirect signers to different landing pages and pass custom query parameters.

    Why this matters (use case):

    We run multiple campaigns and need to send signers to different LPs depending on:

    document template / campaign

    recipient / segment

    region / language

    deal owner / pipeline stage

    We also want to pass tracking parameters such as:

    utmsource, utmcampaign, utm_content

    internal IDs like doc… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Team Dashboard Add Back Button after drilling into someones dashboard

    In Team Dashboard when you select a name and pull up the metrics for the team member, then go into one of the options (ie View) and when you click the back button it does not take you back to the team member dashboad but the Team Dashboad as a whole. Sounds like this is something that PandaDoc has not thought of having a back option so it takes you back to where you last were and not from the start which is not efficient

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating