PandaDoc
PandaDoc is a document automation platform that enables businesses to create, send, track, and e-sign documents programmatically. Their developer platform provides REST APIs and embedded tools for integrating document generation, e-signature collection, and workflow automation directly into third-party applications.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles PandaDoc the way a machine reads it — 97 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — PandaDoc scores 61.1/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile PandaDoc
Each block below is one kind of artifact we hold for PandaDoc. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
PandaDoc API Logs API
Operations for retrieving API request logs useful for debugging and auditing integration activity.
PandaDoc Contacts API
Operations for managing the PandaDoc contacts directory, including creating, reading, updating, and deleting contact records.
PandaDoc Document Attachments API
Operations for managing file attachments associated with a document, including uploading and downloading attachment files.
PandaDoc Document Fields API
Operations for retrieving and updating field values within a document, such as text fields, checkboxes, signatures, and date fields.
PandaDoc Document Link to CRM API
Operations for managing links between PandaDoc documents and external CRM entities such as contacts, deals, or accounts.
PandaDoc Document Recipients API
Operations for managing recipients within documents, including adding, editing, reassigning, and deleting recipients.
PandaDoc Document Reminders API
Operations for configuring automatic reminders sent to document recipients who have not yet completed their actions.
PandaDoc Documents API
Operations for creating, retrieving, sending, and managing the full lifecycle of documents including drafting, sending for signature, downloading, and deleting.
PandaDoc Folders API
Operations for organizing documents and templates into folders, including creating, renaming, and listing folder contents.
PandaDoc Forms API
Operations for retrieving and managing forms, which are publicly shareable document templates that can be filled and signed without a predefined recipient list.
PandaDoc Members API
Operations for managing and retrieving details about workspace members, including listing members and generating member API tokens.
PandaDoc Templates API
Operations for managing document templates, including listing available templates, retrieving template details, creating templates from file upload, and deleting templates.
PandaDoc Webhook Events API
Operations for querying the log of webhook events that have been dispatched, including filtering by type and delivery status.
PandaDoc Webhook Subscriptions API
Operations for managing webhook subscriptions that deliver real-time event notifications for document lifecycle and other platform events.
PandaDoc Workspaces API
Operations for managing organization workspaces, including listing, creating, and deactivating workspaces.
Scroll within the panel for all 15 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
PandaDoc REST API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
PandaDoc GraphQL Schema
This GraphQL schema represents the PandaDoc document automation and e-signature platform. PandaDoc provides REST APIs at `https://api.pandadoc.com/public/v1` for creating, sendi...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Pandadoc Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Pandadoc Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
PandaDoc Webhook Events
The PandaDoc webhook system delivers real-time event notifications to registered subscriber endpoints when document lifecycle and platform events occur. PandaDoc sends HTTP POST...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Pandadoc Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
PandaDoc API Rules
SPECTRALPandaDoc API Rules
SPECTRALJSON Schema 52
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ApiLogListResponse
JSON SCHEMAContact
JSON SCHEMAContactCreateRequest
JSON SCHEMAContactListResponse
JSON SCHEMAContactUpdateRequest
JSON SCHEMAPandaDoc Document
JSON SCHEMADocumentAttachment
JSON SCHEMADocumentAttachmentsResponse
JSON SCHEMADocumentAutoReminderResponse
JSON SCHEMADocumentCreateRequest
JSON SCHEMADocumentCreateResponse
JSON SCHEMADocumentDetailsResponse
JSON SCHEMADocumentField
JSON SCHEMADocumentFieldsResponse
JSON SCHEMADocumentFieldsUpdateRequest
JSON SCHEMADocumentListItem
JSON SCHEMADocumentListResponse
JSON SCHEMADocumentRecipient
JSON SCHEMADocumentRecipientCreateRequest
JSON SCHEMADocumentRecipientsResponse
JSON SCHEMADocumentRecipientUpdateRequest
JSON SCHEMADocumentSendRequest
JSON SCHEMADocumentSendResponse
JSON SCHEMADocumentSessionCreateRequest
JSON SCHEMADocumentSessionCreateResponse
JSON SCHEMADocumentStatus
JSON SCHEMADocumentStatusResponse
JSON SCHEMAErrorResponse
JSON SCHEMAFolder
JSON SCHEMAFolderCreateRequest
JSON SCHEMAFolderListResponse
JSON SCHEMAFormListItem
JSON SCHEMAFormListResponse
JSON SCHEMALinkedObjectsResponse
JSON SCHEMAMember
JSON SCHEMAMemberListResponse
JSON SCHEMATemplateDetailsResponse
JSON SCHEMATemplateListItem
JSON SCHEMATemplateListResponse
JSON SCHEMAPandaDoc Webhook Event
JSON SCHEMAWebhookEventDetails
JSON SCHEMAWebhookEventListItem
JSON SCHEMAWebhookEventListResponse
JSON SCHEMAWebhookEventTrigger
JSON SCHEMAWebhookSharedKeyResponse
JSON SCHEMAWebhookSubscription
JSON SCHEMAWebhookSubscriptionCreateRequest
JSON SCHEMAWebhookSubscriptionListResponse
JSON SCHEMAWebhookSubscriptionUpdateRequest
JSON SCHEMAWorkspace
JSON SCHEMAWorkspaceCreateRequest
JSON SCHEMAWorkspaceListResponse
JSON SCHEMAScroll within the panel for all 52 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Pandadoc Structure
JSON STRUCTURESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for PandaDoc — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/pandadoc · machine-readable index on apis.io