Appearance
PandaDoc
Create, manage, and e-sign documents and proposals via the PandaDoc API.
| Detail | Value |
|---|---|
| Category | Legal |
| Base URL | https://api.pandadoc.com/public/v1 |
| Authentication | API Key |
| Endpoints | 6 |
| Connector key | pandadoc |
Using PandaDoc in a workflow
- Go to Connections and click New Connection.
- Pick PandaDoc from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /documents | List documents |
POST /documents | Create a document |
GET /documents/{documentId} | Get document details |
POST /documents/{documentId}/send | Send a document for signing |
GET /documents/{documentId}/download | Download a completed document |
GET /templates | List templates |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /documents
List documents
| Detail | Value |
|---|---|
| Operation ID | legal.listDocuments |
| Method | GET |
| Path | /documents |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
q | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaDoc connection from the Connection dropdown.
- In the Operation dropdown, select
legal.listDocuments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PandaDoc API reference.
POST /documents
Create a document
| Detail | Value |
|---|---|
| Operation ID | legal.createDocument |
| Method | POST |
| Path | /documents |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaDoc connection from the Connection dropdown.
- In the Operation dropdown, select
legal.createDocument. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PandaDoc API reference.
GET /documents/{documentId}
Get document details
| Detail | Value |
|---|---|
| Operation ID | legal.getDocument |
| Method | GET |
| Path | /documents/{documentId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
documentId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaDoc connection from the Connection dropdown.
- In the Operation dropdown, select
legal.getDocument. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PandaDoc API reference.
POST /documents/{documentId}/send
Send a document for signing
| Detail | Value |
|---|---|
| Operation ID | legal.sendDocument |
| Method | POST |
| Path | /documents/{documentId}/send |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
documentId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaDoc connection from the Connection dropdown.
- In the Operation dropdown, select
legal.sendDocument. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PandaDoc API reference.
GET /documents/{documentId}/download
Download a completed document
| Detail | Value |
|---|---|
| Operation ID | legal.downloadDocument |
| Method | GET |
| Path | /documents/{documentId}/download |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
documentId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaDoc connection from the Connection dropdown.
- In the Operation dropdown, select
legal.downloadDocument. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PandaDoc API reference.
GET /templates
List templates
| Detail | Value |
|---|---|
| Operation ID | legal.listTemplates |
| Method | GET |
| Path | /templates |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaDoc connection from the Connection dropdown.
- In the Operation dropdown, select
legal.listTemplates. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PandaDoc API reference.