# PandaDoc setup for PopMCP

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.

- Auth: API credentials
- Setup time: 6 min
- API base URL: https://api.pandadoc.com/public/v1
- Credentials screen: https://app.pandadoc.com/a/#/api-dashboard/configuration
- Provider docs: https://developers.pandadoc.com/reference/api-key-authentication-process

## Approval required before this 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.

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

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

Screen: https://app.pandadoc.com

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

Screen: https://app.pandadoc.com/a/#/settings/api

### 3. Open Dev center → Configuration

Open Dev center and select Configuration. The direct link is app.pandadoc.com/a/#/api-dashboard/configuration.

Screen: https://app.pandadoc.com/a/#/api-dashboard/configuration

### 4. Create a Sandbox API key

Click Create API key, name it `PopMCP`, select Sandbox and click Create.

Screen: https://app.pandadoc.com/a/#/api-dashboard/configuration

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

Screen: https://demo.pandadoc.com/api-custom-request

### 6. Copy the key into PopMCP

Copy the key from the Configuration page and paste it into PopMCP's API Key field.

## Fields PopMCP asks for

- API Key (apiKey) [required]: 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.

## Verify

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

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: The key belongs to a different PandaDoc workspace.

Fix: Switch to the correct workspace, create a key there, and reconnect PopMCP with it.

---

Source: https://www.docs.popmcp.com/docs/integrations/pandadoc/