How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PandaDoc Document Recipients API

Operations for managing recipients within documents, including adding, editing, reassigning, and deleting recipients.

PandaDoc Document Recipients API is one of 15 APIs that PandaDoc publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Document Recipients. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 7.18.0.

Requests are made against a single base URL, https://api.pandadoc.com/public/v1.

4 operations 2 paths 5 schemas 1 DELETE1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
7.18.0
Base URL
https://api.pandadoc.com/public/v1
Authentication
API Key, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

PandaDoc Document Recipients API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (apiKey). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

  • apiKey — API Key authentication. Include the key in the Authorization header as "API-Key YOURAPIKEY". Generate keys from the PandaDoc Developer Dashboard.
  • oauth2 — OAuth 2.0 authentication. Use the authorization code flow to obtain user-scoped access tokens. Tokens expire after approximately one year.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Document Recipients 4

Operations for managing recipients within documents, including adding, editing, reassigning, and deleting recipients.

GET
/documents/{id}/recipients
List Document Recipients
listDocumentRecipients 1 param → 200401404429
POST
/documents/{id}/recipients
Add Document Recipient
addDocumentRecipient 1 param body → 201400401404429
PATCH
/documents/{id}/recipients/{recipient_id}
Update Document Recipient
updateDocumentRecipient 2 params body → 200400401404429
DELETE
/documents/{id}/recipients/{recipient_id}
Delete Document Recipient
deleteDocumentRecipient 2 params → 204401404429

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are DocumentRecipient (11 properties), DocumentRecipientCreateRequest (7 properties), DocumentRecipientUpdateRequest (4 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

DocumentRecipientUpdateRequest
object
Fields to update on an existing document recipient.
4 properties
DocumentRecipientsResponse
object
List of recipients for a document.
1 property
ErrorResponse
object
Standard error response body.
2 properties
DocumentRecipient
object
A recipient assigned to a document who may be required to sign, approve, or receive a copy of the document.
11 properties
DocumentRecipientCreateRequest
object
Details for a recipient to be added to a document.
7 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pandadoc-document-recipients-api-openapi.yml Raw ↑

Other APIs PandaDoc publishes across the network.

PandaDoc API Logs API
PandaDoc Contacts API
PandaDoc Document Attachments API
PandaDoc Document Fields API
PandaDoc Document Link to CRM API
PandaDoc Document Reminders API
PandaDoc Documents API
PandaDoc Folders API
PandaDoc Forms API
PandaDoc Members API
PandaDoc Templates API
PandaDoc Webhook Events API
Where this information came from

This is an independent, third-party profile of PandaDoc Document Recipients API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.