221 results found

1. API get signature details

   For reporting I want to be able to report on when each recipient signed the document vs when the document was completed by each recipient.

   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

   1 comment  ·  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

2. Pagination ordering 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

3. Expose Cost/Profit margin endpoints in API + Zapier

   Cost/Profit Margin endpoints exposed in PandaDoc 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

4. api revision number as token

   api revision number token for document changes

   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

5. 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.

   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  ·  Edit…  ·  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

6. 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

7. 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  ·  Edit…  ·  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. 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

9. 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

10. 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

11. 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

12. 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

13. 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

14. 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

15. HubSpot Cannot Process PandaDoc Webhooks

    HubSpot requires Record ID's to be ingested as NUMBER type data.

    PandaDoc currently sends custom Webhooks with a "linked_objects" header in the JSON payload, but this is a STRING.

    When building a Custom Event or Webhook Receiver in a HubSpot Workflow, the build attempt will always fail because it cannot parse the STRING or coerce it to NUMBER, and results in a failure to finalize the webhook.

    •  

    •  

    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. Add a Logo to Custom App

    Ability to add a logo to a custom app from the Dev Center.

    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. Reporting: show API document usage per workspace

    Option to see the number of API usage I have in a month and in a year. Break it down by workspace and 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

18. webhooks to detect duplicated documents

    I was wondering if the webhooks can detected dupilcated documents, I am trying to track when a duplicated documents and make a workflow and when I complete a duplicated document it doesn't seem to pick it up when I test the webhook.

    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. Issue with Recipient Group Naming & API Usage

    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 identifier (e.g., a number) to the group name if a duplicate is detected (e.g., "Group Name (1)", "Group Name (2)").

    Allowing API users to explicitly create distinct groups even if names are identical.

    This change would greatly improve data integrity and the reliability of recipient group management, especially for automated workflows.

    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… 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. Enable Send Manual Reminder API for Recipient groups

    Enable Send Manual Reminder API for Recipient groups

    https://developers.pandadoc.com/reference/createmanualreminder

    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