# Dropbox Sign setup for PopMCP

You paste one Dropbox Sign API key into PopMCP, plus the word "test" in the Key type box if it came from a free test-mode API account.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.hellosign.com/v3
- Credentials screen: https://app.hellosign.com/home/myAccount#api
- Provider docs: https://developers.hellosign.com/api/reference/

## Approval required before this works

Production (legally binding) signature requests require a paid Dropbox Sign API plan, and any embedded or OAuth integration must additionally pass Dropbox Sign's app approval review before it can leave test mode.

- Typical wait: Paid plan: instant on purchase. App approval: no SLA published by Dropbox Sign - the docs state no timeframe; submissions are worked through with an API support specialist, so budget days, not minutes
- Cost: App approval is free; production use requires a paid Dropbox Sign API plan (API plans are sold separately from the standard eSignature seat plans - see sign.dropbox.com pricing for current tiers)
- Blocked until approved: Any non-test request. Without a paid API plan the API returns HTTP 402 on production calls, and embedded signing/requesting/templates and OAuth flows stay locked to test mode until the app is approved. Test-mode signature requests are watermarked and are not legally binding.
- Works meanwhile: Everything, in test mode: an API key from the account's API settings works immediately, and test_mode=1 on requests (plus testMode / skipDomainVerification in the embedded client.open() call) exercises the full flow including endpoints otherwise restricted to paid plans. Dropbox Sign explicitly allows completing app approval before buying a plan.

## Before you begin

- Dropbox Sign account. Sign up free at app.sign.dropbox.com.
- Account owner or an admin who can see the API tab. Ordinary team members cannot reveal keys.
- A paid API plan (Essentials or above) if you need real, legally binding signature requests. The free API tier is test mode only.

## Get your credentials

### 1. Open your API settings

Sign in at `app.sign.dropbox.com`, then click API in the left sidebar. The API settings page opens at `app.hellosign.com/home/myAccount#api`.

Screen: https://app.hellosign.com/home/myAccount#api

### 2. Create or reveal your API key

Under API key, click Create Key for a new key, or Reveal Key to show an existing one.

### 3. Copy the key into PopMCP

Click Reveal Key, copy the full string, and paste it into PopMCP's API key field.

### 4. Set the Key type

Type `test` in PopMCP's Key type field if the account is on the free API tier. Leave it blank, or type `live`, on a paid Essentials, Standard or Premium API plan.

## Fields PopMCP asks for

- API key (apiKey) [required]: Dropbox Sign → Settings → API → API Keys → copy your API key (or create one). Stored encrypted; used server-side only via HTTP Basic auth.
- Key type (mode): Enter "test" if this is a free/sandbox API key. Sandbox keys can ONLY create test (non-binding) signature requests, so the connection will auto-send everything in test_mode for you. Leave blank (or "live") for a paid API plan key that sends real, legally-binding documents.

## Verify

PopMCP shows the Dropbox Sign connector as Connected with your account email. Listing signature requests returns real request IDs, and anything created on a test key comes back flagged as test mode.

## Troubleshooting

### 401 Unauthorized

Cause: The key was mistyped or truncated, or it was deleted from Settings, API.

Fix: Reveal the key again in Settings, API, and paste the whole string. If it is gone, click Create Key and use the new one.

### Upgrade required, or non-test requests rejected

Cause: The account is on the free API tier, which can only create test signature requests that are not legally binding.

Fix: Enter "test" as the Key type so PopMCP sends everything in test mode, or upgrade to an Essentials or higher API plan.

### Documents arrive watermarked as a test and cannot be legally signed

Cause: Key type is still set to "test" on a paid plan.

Fix: Clear the Key type field, or set it to "live", and reconnect.

### You cannot see the API tab at all

Cause: You are signed in as a team member rather than the account owner or an admin.

Fix: Ask the account owner to reveal the key, or to grant you admin rights on the Dropbox Sign team.

### Revoking a key broke other tools

Cause: Keys never expire and cannot be moved between accounts, so a shared key is often reused across integrations.

Fix: Issue a separate key per integration and rotate them one at a time.

---

Source: https://www.docs.popmcp.com/docs/integrations/dropbox-sign/