Pandadoc

REST API at api.pandadoc.com/public/v1/. Document creation: POST to /documents with template_uuid, recipients, tokens (merge field values), and pricing items. The template token system is straightforward: define [Token.Name] placeholders in templates, pass key-value pairs in the API call. Recipients are defined with email, role, and signing order. Document sending: POST to /documents/{id}/send. Status tracking: GET /documents/{id} returns current status. Webhook events notify on document state changes (created, sent, viewed, completed). Document download: GET /documents/{id}/download returns the signed PDF. The API also covers contacts, templates listing, and document sections. Folder management organizes documents. The API is simpler than DocuSign's — fewer concepts to learn, faster time to integration.

API errors return JSON with type, detail, and status fields. Standard HTTP status codes. Rate limits: 60 requests per minute for most endpoints. 429 responses include Retry-After header. Document status transitions: draft → sent → viewed → waiting_approval → completed/declined/voided. Webhook delivery retries on failure. The most common agent error: template token mismatches (passing a token that doesn't exist in the template) — the API creates the document but the field is empty rather than returning an error. Agents should validate token names against the template. Document creation from templates can fail if required fields are missing. Signed document download is available only for completed documents. The API is generally predictable and errors are clear.

PandaDoc combines document creation, e-signatures, and proposal management in a more accessible package than DocuSign. For agents, the primary flow is: create a document from a template (filling in merge fields and recipient info), send for signature, and track completion. The API covers document creation (from templates or scratch), recipient management, document sending, status tracking, and signed document download. The template system uses tokens (merge fields) that agents populate with dynamic data — common for sales proposals, contracts, and onboarding documents. Content Library enables reusable content blocks. Pricing tables support CPQ (configure, price, quote) scenarios. For agents managing sales document workflows, PandaDoc's template-based approach is more intuitive than DocuSign's envelope/tab model. The trade-off: less granular control over signing tab placement.

Two auth methods: API key (simpler, for direct integrations) and OAuth 2.0 (for marketplace apps). API key is passed via Authorization: API-Key {key} header. Keys are generated in PandaDoc settings. OAuth uses standard authorization code flow with refresh tokens. For agents, the API key approach is simpler than DocuSign's JWT Grant — no RSA key pair, no consent flow, just generate and use. API keys grant full account access — no fine-grained scoping. Sandbox environment uses separate API keys. For agents building direct integrations, the API key path enables fast onboarding. OAuth is required for integrations distributed to other PandaDoc users. No certificate-based auth or mTLS.

Developer documentation at developers.pandadoc.com is well-organized with API reference, guides, and SDKs. The API reference covers all endpoints with parameters and response examples. Getting started guides walk through document creation, template usage, and webhook setup. SDKs for Python and Node.js are available. Postman collection provides ready-to-use API examples. The documentation is more accessible than DocuSign's — fewer concepts, simpler auth, and clearer examples. CRM integration guides (Salesforce, HubSpot) help agents building connected workflows. The sandbox documentation explains testing without affecting production. For agents, the document creation from template guide is the essential starting point — it covers the most common integration pattern.