PandaDoc
Connect PandaDoc to create documents from templates, send them for signature, and manage recipients, fields, and quotes.
You end up with one PandaDoc API key, a 40-character hex string generated on the Dev center's Configuration page, that you paste into PopMCP's API Key field.
Paid plan required before this connector works
A PandaDoc Production API key must be activated by PandaDoc's own team via Sales, Support or your CSM, and the developer docs state it requires an active Enterprise plan; only the Sandbox key is self-serve.
- Typical wait
- Not published; it depends on a sales or support conversation rather than a review queue
- Cost
- Sandbox key free. Production key documented as requiring an Enterprise plan, which is quote-only pricing from PandaDoc Sales; the API itself is listed for Business and Enterprise tiers.
- Blocked until approved
- With only a Sandbox key you cannot send documents to anyone outside your own email domain, generated PDFs carry a watermark, documents get a [DEV] prefix, and calls are capped at 10 requests per minute per endpoint. No real customer-facing document can be sent until the Production key is activated.
- Works meanwhile
- Generate a Sandbox key in the Dev Center immediately and build and test the whole integration: templates, document creation, recipients within your own domain, webhooks and status polling all work.
Where to apply: Generate keys in the PandaDoc Dev Center (Settings > API and Integrations > Dev Center). For the Production key, existing customers contact Support or their designated CSM; new customers contact PandaDoc Sales.
- PandaDoc's own marketing has announced API access on the free plan with both sandbox and production keys, while the developer reference still says production keys require approval and an Enterprise plan; confirm with PandaDoc which applies to your account before promising a go-live date.
- Sandbox documents cannot be emailed outside your own domain, so end-to-end testing with a real client is impossible before activation.
- Sandbox PDFs are watermarked and titled with a [DEV] prefix, which surprises people who demo the sandbox to stakeholders.
- The key is issued per workspace; a key from one PandaDoc workspace will not read another's templates.
- Setup time
- 6 min
- Auth
- API credentials
- API base URL
- https://api.pandadoc.com/public/v1
- Rate limits
- Sandbox keys are capped at 10 requests per minute per endpoint. Production keys run from about 50 to 2,000 requests per minute depending on the operation, measured over a sliding 60-second window and pooled per user.
Before you begin
- PandaDoc Business or Enterprise plan, or an active trial, for a Sandbox key
- Enterprise plan plus activation by PandaDoc for a Production key
- Org Admin or account owner role. Only they can open the Dev center and generate a key
- A long-lived user account. Removing the user who created a key deactivates that key
Get your credentials
Sign in as an Org Admin and pick the workspace
Sign in at app.pandadoc.com with an Org Admin account. Use the workspace switcher at the top left to select the workspace PopMCP should act on.
Turn on API access in Settings
Click the gear icon at the bottom of the left nav, open API and Integrations, then API, and click Enable. Enterprise accounts can skip to the next step.
API and Integrations
Turn on API access to unlock the Dev center for this workspace.
Enterprise workspaces have the Dev center on already.
Open Dev center → Configuration
Open Dev center and select Configuration. The direct link is app.pandadoc.com/a/#/api-dashboard/configuration.
Configuration
API keys, OAuth 2.0 applications and webhook subscriptions for Acme HQ.
| Name | Type | Key | Created by | Status | Created |
|---|---|---|---|---|---|
| Zap integrationAcme HQ | Sandbox | 3039ba03****02cd8 | dana@acme.com | Active | Mar 4, 2026 |
| Billing syncAcme HQ | Production | 8c17ffa2****41b70 | sam@acme.com | Inactive | Jan 11, 2026 |
Keys are listed per workspace. A key can only reach documents, templates and contacts in the workspace it was created in.
Create a Sandbox API key
Click Create API key, name it PopMCP, select Sandbox and click Create.
Configuration
API keys, OAuth 2.0 applications and webhook subscriptions for Acme HQ.
The key inherits the role and licence of the Org Admin who creates it.
Ask PandaDoc to activate a Production key
To send real documents, contact your PandaDoc CSM or Support and request a Production key on your Enterprise plan.
Copy the key into PopMCP
Copy the key from the Configuration page and paste it into PopMCP's API Key field.
Configuration
- Header
- Authorization: API-Key 3039ba03****02cd8
- Base URL
- https://api.pandadoc.com/public/v1
Sandbox keys stay readable on the Configuration page. Treat them as secrets anyway.
Connect in PopMCP
Open your workspace, choose PandaDoc in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API Keysecret | Generate it in PandaDoc → Developer Dashboard → Configuration (app.pandadoc.com/a/#/api-dashboard/configuration). A Sandbox key works on Business/Enterprise plans (test documents, watermarked PDFs, 10 req/min); a Production key needs Enterprise + activation. Sent as the Authorization: API-Key header, stored encrypted, used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against PandaDoc immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows the connection as Connected and listing templates or documents returns your PandaDoc workspace's real items. With a Sandbox key, new documents appear in PandaDoc with a [DEV] prefix.
Troubleshooting
401 Unauthorized
Why: The key is wrong, was deactivated because its creator left the workspace, or you are calling a Production-only endpoint with a Sandbox key.
Fix: Create a new key from an Org Admin account that stays in the workspace, or request a Production key for the endpoints that need one.
Dev center is not in the left nav
Why: API access has not been enabled for this workspace on a Business plan.
Fix: Go to Settings, API and Integrations, API, then click Enable.
403 Forbidden on org-level actions
Why: The key was generated by a user without Org Admin rights.
Fix: Have an Org Admin create a fresh key on the Configuration page and replace it in PopMCP.
Documents come out watermarked with a [DEV] prefix
Why: You are using a Sandbox key, which is the intended behaviour for testing.
Fix: Request a Production key from PandaDoc once you are ready to send live documents.
429 Too Many Requests
Why: Sandbox keys are capped at 10 requests per minute per endpoint, and limits are pooled per user across all their keys.
Fix: Slow the request rate, or move to a Production key whose limits run from roughly 50 to 2,000 requests per minute.
Documents or templates are missing
Why: The key belongs to a different PandaDoc workspace.
Fix: Switch to the correct workspace, create a key there, and reconnect PopMCP with it.