Skip to content
For LLMsView as Markdown·

PandaDoc

Create, manage, and e-sign documents and proposals via the PandaDoc API.

DetailValue
CategoryLegal
Base URLhttps://api.pandadoc.com/public/v1
AuthenticationAPI Key
Endpoints6
Connector keypandadoc

Using PandaDoc in a workflow

  1. Go to Connections and click New Connection.
  2. Pick PandaDoc from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET /documentsList documents
POST /documentsCreate a document
GET /documents/{documentId}Get document details
POST /documents/{documentId}/sendSend a document for signing
GET /documents/{documentId}/downloadDownload a completed document
GET /templatesList templates

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /documents

List documents

DetailValue
Operation IDlegal.listDocuments
MethodGET
Path/documents

Parameters

NameLocationTypeRequired
qquerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your PandaDoc connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listDocuments.
  4. 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

DetailValue
Operation IDlegal.createDocument
MethodPOST
Path/documents

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your PandaDoc connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.createDocument.
  4. 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

DetailValue
Operation IDlegal.getDocument
MethodGET
Path/documents/{documentId}

Parameters

NameLocationTypeRequired
documentIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your PandaDoc connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.getDocument.
  4. 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

DetailValue
Operation IDlegal.sendDocument
MethodPOST
Path/documents/{documentId}/send

Parameters

NameLocationTypeRequired
documentIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your PandaDoc connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.sendDocument.
  4. 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

DetailValue
Operation IDlegal.downloadDocument
MethodGET
Path/documents/{documentId}/download

Parameters

NameLocationTypeRequired
documentIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your PandaDoc connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.downloadDocument.
  4. 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

DetailValue
Operation IDlegal.listTemplates
MethodGET
Path/templates

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your PandaDoc connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listTemplates.
  4. 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.