160 results found

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

   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

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

3. Support phone-only recipients for embedded signing session endpoint

   The ability to use a phone number (E.164 format) in place of an email address in the recipient field of the POST /documents/{id}/session endpoint.

   Currently, the endpoint only accepts an email address.

   For cases where recipients have no email address on file and the app handles the signing experience directly.

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

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

6. Create Bundled Products via API

   the ability to create bundled products via API

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

8. Pull Data Fields from documents via API or Webhooks

   the ability to pull data fields from contracts via API or Webhooks

   3 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

9. An API endpoint for updating Content Library items
   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

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. Public API Endpoint to enable/activate Stripe payments

    Request to have a public API endpoint to enable Stripe payments without manually doing it in the UI.

    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

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

14. Extend the “Template Updated” webhook trigger to cover updates to templates fields

    At the moment, the "Template updated" webhook trigger includes the following events:

    Changes to template name
    Changes to template roles
    Addition of a section

    The feature request is to extend the “Template Updated” webhook trigger scope to cover updates to templates fields (or possibly introduce a separate trigger "Template updates (fields)".

    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

15. API: Sender parameter take precedent over owner parameter

    If the email specified in the sender parameter does not match an existing workspace user, PandaDoc may automatically assign the document to the default workspace sender. In PandaDoc, the document owner always takes precedence over the sender parameter if the sender does not match the document owner or meet workspace requirements. Even if your API call sets a different sender, the document will still be sent from the document owner.

    Would like this to not occur, and allow for the sender perimeter to set the sender email

    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

16. API Endpoint to Retrieve Workspaces for a Specific User

    Request for a new API endpoint that returns all workspaces associated with a specific user within an organization.

    Example desired functionality:

    GET /users/{user_id}/workspaces

    or

    GET /user-workspaces?user_id={id}

    This would allow integrators to dynamically determine which workspaces a user belongs to without retrieving the full user list across the organization.

    Customer Context

    Customer operates a franchise model with:

    40+ workspaces

    500+ users

    Shared identity across the organization

    Heavy API-based embedded document workflows

    Users may belong to multiple workspaces simultaneously.

    The customer initiates document creation from their CRM and needs to determine which workspace the user should interact with before creating the document.

    Current Limitation

    The current API architecture does not provide a direct method to retrieve the workspaces associated with a specific user.

    The only available approach is:

    Retrieve all users in the organization

    Parse the full list

    Determine which workspaces the target user belongs to

    For organizations with hundreds of users, this approach is:

    Inefficient

    Resource intensive

    Difficult to scale

    Request for a new API endpoint that returns all workspaces associated with a specific user within an organization.

    Example desired functionality:

    GET /users/{user_id}/workspaces

    or

    GET /user-workspaces?user_id={id}

    This would allow integrators to dynamically determine which workspaces a user belongs to without retrieving the full user list across the organization.

    Customer Context

    Customer operates a franchise model with:

    40+ workspaces

    500+ users

    Shared identity across the organization

    Heavy API-based embedded document workflows

    Users may belong to multiple workspaces simultaneously.

    The customer initiates document creation from their CRM and needs to determine which workspace the user should interact with before creating the document.

    … 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

17. Export All Catalog Items via the API

    Currently, users are using the existing “List Catalog Items Search” endpoint to retrieve and export all catalog items via the API. However, this endpoint was originally designed as a search endpoint, intended to filter a relatively small subset of items based on a specific query. It was not built to reliably return the entire catalog, which can lead to limitations and unintended errors when used as a full listing mechanism.

    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

18. Allow uploaded .DOCX files to be editable using https://www.npmjs.com/package/pandadoc-editor

    It's currently not possible to make uploaded .docx file editable using the PandaDoc Editor NPM Library: https://www.npmjs.com/package/pandadoc-editor
    We would like it to work the same way as within the native PandaDoc application.
    we should be able to make .docx files editable using this NPM Library

    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

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