PandaDoc API

Name: PandaDoc API
Brand: PandaDoc API
Availability: InStock

✓ Official Vendor SpecProductivityNote TakingapiKey116 EndpointsREST

For Agents

Automate PandaDoc document creation, sending, signing, and tracking - from templates, PDFs, or dynamic content with placeholders, webhooks, and form data extraction.

Install Jentic One Beta

Connect the PandaDoc API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PandaDoc API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PandaDoc API.

Create documents from templates with dynamic content placeholders and variable substitution

Upload and send local PDFs for signature with recipient roles and field positioning

Configure recipients with signing order, authentication, and role-based field access

GET STARTED

Start building with PandaDoc API

Explore with Jentic

View OpenAPI Document

PandaDoc API enables document automation for proposals, quotes, contracts, and e-signature workflows. The API covers document creation from templates or PDF uploads, dynamic content placeholders, recipient configuration, sending for signature, tracking status changes, webhook subscriptions, form field data extraction, content library management, template CRUD, folder organization, analytics, and user administration. Authentication uses API keys (API-Key prefix) or OAuth 2.0 for user-delegated access. The API supports high-volume document generation with rate limits scaled by plan tier.

Use Cases

Patterns agents use PandaDoc API for, with concrete tasks.

★ Generate and Send Contracts from CRM Data

Automate contract generation by pulling data from a CRM like Salesforce or HubSpot and creating PandaDoc documents from templates. POST /documents with template_uuid and tokens (placeholders like {Client.Name}, {Deal.Value}) generates a document, then POST /documents/{id}/send delivers it to recipients for signature. This eliminates manual copy-paste and ensures contract accuracy.

POST /documents with template_uuid and tokens object mapping placeholders to CRM values, then POST /documents/{id}/send with recipients and subject.

Upload and Send Local PDFs for Signature

Upload a PDF contract or agreement that does not originate from a PandaDoc template and send it for signature. POST /documents with a multipart file upload and recipient configuration allows dynamic PDF signing workflows. This supports scenarios where legal teams provide pre-formatted PDFs that need e-signature without template redesign.

POST /documents with file upload and recipients, then POST /documents/{id}/send to deliver for signature.

Real-Time Document Status Tracking via Webhooks

Subscribe to PandaDoc webhooks to receive real-time notifications when documents are viewed, completed, voided, or declined. POST /webhooks/subscriptions with event types (document_state_changed) and a callback URL enables integrations that trigger downstream workflows like updating CRM deal stages, notifying sales reps in Slack, or releasing product access when a contract is signed.

POST /webhooks/subscriptions with event types ['document_state_changed'] and callback URL to receive status updates.

Extract Form Field Data from Completed Documents

After a document is completed, extract form field values and signature data for downstream processing like populating databases, generating invoices, or triggering fulfillment. GET /documents/{id}/fields returns all field names and values, including text inputs, checkboxes, dropdowns, and signature timestamps. This supports automated order processing and data capture workflows.

GET /documents/{id}/fields after document status is 'document.completed' to extract field names and values.

AI Agent for Document Workflow Automation

Let an AI agent handle document lifecycle tasks like creating contracts from customer data, sending for signature, tracking status, notifying stakeholders, and extracting signed data. Through Jentic, the agent searches by intent (e.g., 'create pandadoc document from template'), loads the schema, and executes with the API key injected securely, enabling conversational document automation.

Use Jentic search 'create pandadoc document from template' to find POST /documents, load schema, execute with template_uuid and tokens.

Key Endpoints

116 endpoints — pandadoc api enables document automation for proposals, quotes, contracts, and e-signature workflows.

METHOD

PATH

DESCRIPTION

POST

/documents

Create a document from template or PDF

POST

/documents/{id}/send

Send a document for signature

GET

/documents

List documents with filters

GET

/documents/{id}

Get document details

GET

/documents/{id}/fields

Extract form field values

POST

/webhooks/subscriptions

Subscribe to document events

GET

/documents/{id}/download

Download completed document as PDF

POST

/documents

Create a document from template or PDF

POST

/documents/{id}/send

Send a document for signature

GET

/documents

List documents with filters

GET

/documents/{id}

Get document details

GET

/documents/{id}/fields

Extract form field values

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your PandaDoc key is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a PandaDoc document from a template' or 'send a document for signature', and Jentic returns the matching PandaDoc operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using PandaDoc API through Jentic.

What authentication does the PandaDoc API use?

The PandaDoc API uses API key authentication with the Authorization header (format: 'API-Key <your-key>') or OAuth 2.0 for user-delegated access. Through Jentic, API keys are stored encrypted and injected at execution time.

Can I create documents from templates with the PandaDoc API?

Yes. POST /documents with template_uuid and a tokens object containing placeholder values creates a document from a template. This supports dynamic contract and proposal generation from CRM or database data.

How do I send a document for signature via the PandaDoc API?

After creating a document, call POST /documents/{id}/send with recipients, subject, and optional message. Recipients receive an email with a signing link, and status updates are tracked via webhooks or polling.

Does the PandaDoc API support webhooks?

Yes. POST /webhooks/subscriptions with event types like 'document_state_changed' and a callback URL enables real-time notifications for document status changes, signature completions, and form field updates.

Is the PandaDoc API free?

PandaDoc offers a sandbox environment for testing on Enterprise plans. Production API access is included with Business and Enterprise plans. Rate limits and features vary by plan tier. Check pandadoc.com/pricing for details.

Can I upload a PDF and send it for signature?

Yes. POST /documents with a multipart file upload allows you to upload a local PDF, configure recipients and fields, then send for signature. This supports PDFs that do not originate from PandaDoc templates.

Can I limit what my agent is allowed to do with the PandaDoc API?

Yes. Jentic One runs self-hosted, so your own rules decide which PandaDoc operations the agent may call, meaning read-only actions like GET /documents/{id} can be allowed while POST /documents/{id}/send stays off until you approve it. Because PandaDoc puts the document id in the URL path, such as /documents/{id}/send, a rule can pin the agent to a specific document rather than every document in the account. Your API key is held by your own instance and injected only for the operations you permit, so the agent cannot send a document for signature unless you add that operation.

PandaDoc API

Connect the PandaDoc API to your agent

Capabilities

Start building with PandaDoc API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs